End-of-life badge for your README
Show at a glance whether the Node.js, Python, PostgreSQL or any of 450+ technologies your project depends on is still supported. The badge is a live SVG image: it turns orange 90 days before end of life and red once the version is EOL — no maintenance needed.
Examples
Generate your badge
[](https://eolcanary.com/explore/nodejs/22)
How it works
The badge URL follows the pattern https://eolcanary.com/badge/<technology>/<version>.svg. Use the technology slug from its Explore page URL, and either a major version (nodejs/22) or an exact cycle (python/3.12).
Each request computes the status from the same end-of-life data as the rest of EOLCanary. When you update your dependency, just change the version in the URL. Clicking the badge opens the version page with its EOL dates and known CVEs.
Frequently asked questions
Is the EOL badge free?
Yes. Badges are free, need no account and no API key. Use them in public or private repositories, documentation or internal wikis.
How often is the badge updated?
End-of-life dates are synced daily from endoflife.date. Badges are cached for 6 hours, so a status change shows up within a few hours. GitHub also caches images through its camo proxy.
Should I use a major version or an exact cycle?
Use the major version (e.g. nodejs/22) when the whole series shares one support policy. Use the exact cycle (e.g. python/3.12) when each minor release has its own end-of-life date, as with Python, Kubernetes or PostgreSQL.
What do the colors mean?
Green: the version is supported. Orange: it reaches end of life within 90 days. Red: it is past end of life and no longer receives security fixes. Grey: unknown product or version.
Can I get notified instead of checking the badge?
Yes. Create a free EOLCanary project with your stack and you will receive an email 6 months, 3 months, 1 month and 1 week before each version reaches end of life, plus alerts on new critical CVEs.
