How the score works
Every listed project gets a health score from 0 to 100, recomputed weekly from its GitHub activity. It answers one question — would you bet a business on it?
Stars are a popularity trophy. Health tells you whether the project is being maintained right now.
The five signals
| Signal | Max | How it scores |
|---|---|---|
| Commit recency, default branch | 30 | 7 days or less: 30 · 30 days: 25 · 90 days: 15 · 180 days: 5 · older: 0 |
| Release cadence, releases in the last 180 days (tags if there are no releases) | 20 | 6 or more: 20 · 3–5: 15 · 1–2: 8 · none: 0 |
| Issue throughput, closed ÷ opened in the last 90 days | 20 | 1.0 or better: 20 · 0.7: 14 · 0.4: 7 · lower: 0 · fewer than 5 opened: 14 |
| Contributor breadth, distinct commit authors in the last 90 days | 20 | 10 or more: 20 · 5–9: 15 · 2–4: 10 · 1: 4 |
| Momentum, star growth over 90 days | 10 | 5% or more: 10 · 1%: 6 · any: 3 · none: 0 |
Two overrides: an archived repository scores 0, and a project with no commits in a year is capped at 20.
The bands
- 80 and up: healthy
- 60–79: steady
- 40–59: slowing
- Under 40: at risk
How ranking works
Lists are ordered by health score, highest first, with stars as the tiebreaker. Stars are shown but never used to rank. Sponsored placements sit in their own labeled slot and never change a project’s rank.
We keep every weekly score, which is where the commit heatmaps and trend lines come from. The weights may be retuned as we learn; when they change, this page will say so.
See what we list for the rules a project has to meet before it’s scored at all.