How grades work
Every listing gets letter grades from A to F for maintenance, licence and quality, calculated daily from public repository and registry data. Each grade shows its reason on the listing page. A security grade from a full file scan is rolling out next.
| Grade | A | B | C | D | F |
|---|---|---|---|---|---|
| Maintenance | Last commit within 30 days | Within 90 days | Within 6 months | Within a year | Older than a year |
| Licence | Permissive (MIT, Apache, BSD, ISC, MPL) | Other known licence | Copyleft (GPL, AGPL) | Not used | No licence found |
| Quality | 5 of 5 checks | 4 of 5 | 3 of 5 | 2 of 5 | 0 or 1 |
Questions
What are the 5 quality checks?
A clear description, a published package or server URL (or a GitHub install for skills), at least 50 GitHub stars, 500 or more stars counting as a second point, and an original repository that is not a fork.
Is the security grade live?
Not yet. The security grade reads every file in the project and flags hidden or encoded instructions, download-and-run steps, code that sends files or keys over the network, and permissions broader than the tool needs. It is rolling out listing by listing, and each grade will show its reasons.
Can I pay for a better grade?
No. Grades come from public data only. Sponsors never affect grades or rankings.
How do I improve my grade?
Commit regularly, add an open source licence, write a clear description and publish a package or server URL. Grades update daily.