Six panels. No algorithm.

One sign-in, read-only. We ask for the narrowest scope GitHub offers — read:user — which cannot write anything, anywhere, ever. Revoke it from your GitHub settings whenever you like and ask us to drop your row with it.

• Your public profile and avatar
• Your contribution calendar for the last 365 days
• Your code. Not one line, public or private
• Permission to write, push, or open anything

The same contribution calendar GitHub prints on your profile for the entire internet. Nothing is computed that you could not recompute yourself, which is the point — a board you cannot check is just someone’s opinion with a number next to it.

quietshipping

That is the whole ranking. Your total contributions in the window — commits, pull requests, issues, reviews — exactly as GitHub counts them. No weighting, no bonuses, no adjustment, no tiebreaker.

A streak is consecutive days with at least one contribution. You can narrow the board to people currently on a run — 7+, 30+, 100+ days — but filtering only removes rows. It never reorders them.

The moment a board has two ranking signals, it has a hidden algorithm and stops being checkable. So the second number is a control you hold, not a thumb we put on the scale.

You need 20 active days in a year to be ranked (8 over 30, 3 over 7), so a one-day account cannot buy first place. Everyone under the floor still appears, marked unranked.

Hiding people is how a leaderboard starts lying. Every row links to the GitHub profile it was computed from — if a number looks wrong, go and check it.

That is the entire product. Seeing someone one place above you is the fastest way to stop being lazy, and a streak is the same trick aimed at tomorrow: once you are eleven days in, the twelfth is easier than the argument for skipping it.