Ranking
Which releases compete for Release of the Day, Week and Month, and how they're scored.
Coding agents: read this page as markdown.
Every published release appears in the feed and reaches the project’s followers. Releases that meet the eligibility rules also compete for Release of the Day, Release of the Week and Release of the Month.
Eligibility #
A release is ranked only if all of these are true:
| Rule | Why |
|---|---|
| It’s a minor or major version, or the project’s first release | Patch releases would flood the boards |
| It was released on GitHub within the last 14 days | Old releases can’t be published as new |
| It has a real changelog and a hero that passes every check | See Release requirements |
| The project has no other release in the same period | One entry per project per day, week and month |
A release is compared with the previous final release of its own tag
series: in a repository that tags v1.2.0 for one thing and
apps/cli/v0.3.0 for another, v1.2.1 follows v1.2.0, whatever was
released in between, and a release candidate doesn’t count as the previous
release. The first release of a new tag series in a project that already
has releases isn’t ranked.
Releases that aren’t eligible are still published and still reach followers. The check endpoint tells you which rule failed.
Scoring #
Rankings come from people browsing the site:
- Votes are weighted. Each vote counts according to the voter’s own GitHub account: its age and its history. A brand-new account’s vote counts for nothing, which is what a vote ring is made of. A voter’s track record of spotting good releases early isn’t part of the weight yet; it is planned.
- Votes are compared with views. A release’s score is its weighted votes divided by how many people actually saw it, smoothed toward the site average. Three votes from ten views won’t beat forty from three hundred.
- Every new release gets a fair first look. For its first two days, or until about a hundred people have seen it, an eligible release has places kept for it in the home feed and is listed under fresh.
Boards #
| Board | Period (UTC) | Decided by |
|---|---|---|
| Release of the Day | The day the release was posted | Its score 24 hours after posting |
| Release of the Week | ISO week | Its score, two days after the week ends |
| Release of the Month | Calendar month | Its score, two days after the month ends |
A release competes in the period it was posted in, and a board needs a minimum of votes: under it, nobody places.
Placements are permanent and appear on your project page. A README badge links back to your best placement.
What can’t affect ranking #
- Money. There’s no paid placement, ever. Sponsored slots, if they come, are labelled and never change a ranking.
- The API. API tokens can’t vote, follow or save.
- Engagement tricks. Time spent on cards and clicks shape the order of the home feed, but never the boards.