How the maintenance score works
The whole formula, published. No black box: the site generator builds this page from the same constants the scoring code uses, so what you read here is what runs.
The four components (total 100 points)
1. Last commit — up to 40 points
| last commit within 30 days | 40/40 |
| last commit within 90 days | 32/40 |
| last commit within 180 days | 24/40 |
| last commit within 365 days | 12/40 |
| last commit within 730 days | 4/40 |
| older, or repository archived | 0/40 |
2. Latest release — up to 25 points
| latest release within 90 days | 25/25 |
| latest release within 180 days | 19/25 |
| latest release within 365 days | 12/25 |
| latest release within 730 days | 5/25 |
| older or no releases | 0/25 |
3. Community size (GitHub stars) — up to 15 points
| 20,000+ stars | 15/15 |
| 5,000+ stars | 12/15 |
| 1,000+ stars | 9/15 |
| 250+ stars | 5/15 |
| 50+ stars | 2/15 |
| fewer | 0/15 |
4. Open-issue trend — up to 20 points
| open issues falling (≤ −5%) | 20/20 |
| stable (−5% to +5%) | 14/20 |
| rising (+5% to +25%) | 7/20 |
| rising sharply (> +25%) | 2/20 |
| insufficient history (needs snapshots 21+ days apart) — neutral score, clearly labeled | 10/20 |
The trend compares snapshots taken on different weekly refreshes, at least 21 days apart. A brand-new listing honestly cannot have a trend yet, so it gets a labeled neutral score until enough history accumulates — you will see that stated on the card rather than a made-up number.
Labels
| 80+ points | actively maintained |
| 60+ points | maintained |
| 40+ points | slowing down |
| 20+ points | stagnant |
| 0+ points | looks abandoned |
Archived repositories are always labeled abandoned (repository archived) regardless of points.
The "looks unmaintained" flag
Any project — including the well-known tool a page is about, when it is open source — gets flagged "looks unmaintained since <date>" when its repository is archived or has had no commits for over 365 days. The date shown is the last recorded activity.
Where the data comes from
Everything is fetched from GitHub's public API and public release feeds — repository metadata (stars, open issues, last push, archived status) and the latest release per project — without authentication, inside GitHub's public rate limits, weekly. Each card shows its own fetch date. Latest run: 2026-09-04, 190 repositories refreshed.
Honest limitations
- Stars measure popularity, not quality — that's why they're only 15 points.
- GitHub's open-issue count includes open pull requests (that is how the API reports it); the trend compares like with like.
- A calm mature project can score below a hyped new one. Read the breakdown, not just the number.
- Projects developed off GitHub (e.g. on GitLab) are listed without scores and say why, instead of carrying misleading mirror numbers.