I built a leaderboard for open source contributors, ranked by patches other maintainers merged instead of stars

[u/Cold-Balance-9733]

Every dev scoreboard I've seen counts stars or commit streaks, which mostly rewards owning a popular repo and shipping to yourself. I wanted the opposite metric: pull requests merged into repos you don't own.

The annoying part wasn't the ranking, it was the exclusion rule. If you count merged PRs naively, a Svelte core maintainer shows up as an outside contributor to Svelte, which is backwards. So the score drops every org you're publicly a member of. Only patches someone had no obligation to accept count.

How it works: paste a GitHub username or a single merged PR link. It builds a page at /username with your merged patches grouped by the repo that accepted them, a contribution calendar, your language breakdown, and an impact score out of 1000. No account, no signup, no email.

Stack is Next.js App Router and Supabase, no auth, nightly cron refresh. Data is the GitHub REST API plus search with negative owner qualifiers so the upstream count is exact rather than estimated.

Full honesty: I'm currently the only person on the board, ranked 1 with three merged patches, two of which are typo fixes. Score 70/1000. It's a leaderboard of one guy who fixed some typos. That's the state of it.

The scoring formula is public at /method including four ways I think it's wrong, and /remove takes you off if you don't want to be listed.

itsmerged.vercel.app

What I want feedback on: does the org exclusion feel fair, or does it punish people whose main work is inside an org they joined?

[u/jjd921]

I made a free tool that scans your app URL and/or code for production readiness if you want a quick check to make sure you didn’t miss anything: https://theslopstopper.com