Contributor record
Top contributors
Ranked by issues accepted upstream, never by token volume. The table opens after the first independent merge, so there are no seeded rows to discount.
Sort order: accepted issues, then independent repositories helped, then the smaller median diff, then GitHub numeric id. 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. Provider usage is reported separately 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.
It is not a primary ranking input because it 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 accepted issues across the same number of repositories, the smaller median wins, which rewards the smallest change that actually fixed the issue.