Software End-of-Life Checker
See when Node.js, Python, Ubuntu and 470+ other products reach end of life, with the days left for every version.
Software End-of-Life Checker tool
Example
Input: Product Node.js, your version 18.19 (checked on September 25, 2026)
Result: Node.js 18.19 belongs to the 18 release line, which reached end of life on Apr 30, 2025, so it no longer gets security fixes. Commercial Support is still offered. A supported line is 24 (LTS), latest release 24.21.0. A newer patch in this line is available: 18.20.8.
From the live endoflife.date record for Node.js. Version 18.19 matches the 18 line, whose end-of-life date has passed. The tool suggests the newest supported LTS line.
What Each Status Means
| Status | Rule used | What still gets fixed |
|---|---|---|
| Supported | Released and still in full support | Bugs and security issues |
| Security fixes only | Active support ended, end of life not reached | Security issues only |
| End of life | End-of-life date has passed | Nothing (paid extended support may exist) |
| Not released yet | Release date is in the future | Not applicable |
Dates are compared with today in your time zone.
- Type a product name, such as Node.js or Ubuntu, and pick it from the list, or tap one of the popular products.
- Read the table: each release line shows its status, the days left or the days since support ended, the end dates and its newest release.
- Look for the Latest and LTS labels to find the newest line and the long-term support lines.
- To check your own install, enter its version (for example 18.19) in the Your version box and click Check version.
- Click Copy table to paste the dates into a ticket or upgrade plan, and follow the release policy link to confirm them with the vendor.
End-of-Life Dates and Why They Matter
Pick a product and this checker lists every release line with its status today: supported, security fixes only, or end of life. Each line shows how many days of support are left, or how long ago support ended. The dates come from endoflife.date, a free, community-run database. It tracks more than 470 products, from Node.js and Python to Ubuntu, PostgreSQL and Kubernetes.
End of life (EOL) means the vendor stops shipping fixes, including security patches. New flaws found in an EOL version will never be patched, which is why security audits flag it. Many projects also have a middle phase. Node.js and Python call the first phase Active Support and the second Security Support. In the second phase, bugs stop being fixed, but security holes still are. The table uses each product's own phase names as column headings. It marks the newest line as Latest and flags LTS (long-term support) lines.
To check a real install, type its version, such as 18.19 or v22.1.0. The tool matches it to its release line and tells you whether that line is still supported. It also says when a newer patch exists in the same line. If your line has ended, it points you to a supported one, preferring an LTS line.
Days are counted from today's date in your own time zone. Your browser loads the product list once, then fetches a product's dates when you pick it. Only the product name is sent to endoflife.date. Volunteers update the data from vendor announcements, so a brand new release can take a few days to appear. Some products never publish end dates, and those rows say so. Before a big upgrade decision, confirm the dates with the vendor. The tool links to the release policy page when one is known.
Upgrading because a runtime is out of support? Check the packages you depend on as well with the Package Vulnerability Checker.
Sources
Frequently Asked Questions
Related Tools
Package Vulnerability Checker
Check npm, PyPI, Maven, Go and other packages for known vulnerabilities and CVEs, and see which version fixes each.
Developer Toolsnpm Package Size Checker
See the minified and gzipped size of any npm package, its download time, dependency count and whether it tree-shakes.
Developer ToolsDocker Run to Docker Compose Converter
Convert docker run commands to docker-compose.yml format with proper YAML structure and service configuration.
DevOps Tools