Top contributors
Ranked by issues merged upstream, never by token volume. The board opens after the first independent merge, so there are no seeded rows to discount.
How ranking worksMerged work leads; token use never improves rank.
Sort order: merged issues, then independent repositories helped, then the smaller median diff, then GitHub numeric id. Diff is the total: every line of every merged pull request, added and removed, as GitHub reports it. Work in a repository under the contributor’s own account, work they merged themselves, and owners the operator has declared are all excluded — decided from the pull request itself, not from anything the contributor’s own machine claims about it. Token burn has its own column as bounded, contributor-reported usage and never improves rank.
Why diff size is a tie-break, not a rank
Sloppy measures every patch twice: the raw change, and the change with lockfiles, vendored trees, fixtures, snapshots and maintainer-declared generated output removed. The second number is what the 20-file / 400-line budget gates on, so a regenerated lockfile never disqualifies a two-line fix.
Neither number is a primary ranking input, because diff size is gameable in both directions: a contributor can pad a diff or split one fix across many pull requests. Among contributors with the same number of merged issues across the same number of repositories, the smaller median wins, which rewards the smallest change that actually fixed the issue. The column shows the total instead of that median, because a total is the one figure that adds up — it is a record of how much landed, not a claim about how it ranked.