Why we rank by shipping

One question: is someone working on this, recently and steadily? We answer it from what GitHub records when code is pushed. Nobody self-reports.

For people choosing software. You're betting someone will be there next month. Stars, upvotes, polished sites and "actively maintained" can't tell you, because none of them change when work stops. Steady recent shipping can. It's a sign, not a guarantee.

For builders. Showing up is what you compete on. One person can reach every target. Your score moves only when you ship, and nobody can buy a rank. That's why yours is worth showing.

What each part rewards

• Consistency (400): days shipped. Hardest to fake, so it counts most.
• Velocity (300): commits per week, on a flattening curve that stops at 50.
• Build size (150): lines changed, capped because lines are easy to inflate.
• Releases (150): work that reached users, up to 3 a week.

Recent days count most. We use the time code was pushed, not the date on the commit, so streaks can't be backdated. Automation bots, lockfiles and generated code are filtered out. Coding-agent commits count, and the caps keep volume from paying.

What we leave out

Stars, upvotes, clicks, money and self-reported numbers. They measure attention, audience or budget, not ongoing work, and some can be bought.

What a rank doesn't tell you

Whether software is good, secure or right for you. Quiet can mean finished. A rank says one thing: someone is shipping, and we checked.

The full formula, every rule and its changelog are on How scoring works.