Methodology
How each number gets onto the page.
Written once by us
Type, language, database, hosting, licence, backer, year started, ten yes/no features and the best-for / not-for verdict. Reviewed once a year, or after a major release.
Fetched every week
A job runs every Monday and updates only the fetched fields.
| Data | Source | Schedule |
|---|---|---|
| Releases, contributors | GitHub API | Weekly |
| Downloads | npm, Packagist, PyPI, Docker Hub | Weekly |
| Security advisories | OSV.dev | Weekly |
| Health score | OpenSSF Scorecard (deps.dev) | Weekly |
| Supported versions | endoflife.date | Weekly |
| Market share, Core Web Vitals | HTTP Archive | Monthly (the source updates monthly) |
When a fetch fails
The old value stays, the page shows when it was last checked, and the failure goes into a weekly report.
SaaS products
Hosted products such as Contentful, Webflow and Wix have no public repository, so release, health and advisory columns read n/a. Their usage and Core Web Vitals still come from HTTP Archive.
Related articles
A blog post tagged with a CMS appears on that CMS's page, and the post shows current figures for every CMS it is tagged with.