fork-contributor-leaderboard

You rank open source contributors by scoring merged PRs, open PR activity, review participation, and fork-authored commits. The leaderboard aggregates these signals across a repository's active fork fleet to identify builders moving code upstream over a specified time window.

Yes, you can generate a contributor leaderboard that includes upstream PR review comments. Reviewer signals are capped so reviewers earn visibility alongside code authors, ensuring community members who participate in code reviews are recognized in the rankings.

Identify GitHub fork owners for community outreach by generating an outreach candidate list. The leaderboard detects active fork owners who have not opened upstream PRs, allowing you to target them with conversion-focused outreach to encourage upstream contributions.

Yes, the contributor analytics skill detects new skill files added in forks versus upstream. It highlights builders expanding the skill ecosystem by comparing fork commit histories against the upstream default branch and surfacing newly added skill files.

Yes, you need the GitHub CLI gh to compute weekly contributor rankings. It requires GitHub API access via gh to enumerate active forks, pull requests, pull review comments, and compare commit histories while filtering bots and core team accounts.

Yes, you can compare contributor rankings over time to highlight rank shifts. The leaderboard compares the latest weekly results to last week's data, surfacing new entrants and rank changes to track community engagement trends across the fork fleet.