Skip to content

EndOfLifeDate

Dennis Lee edited this page May 27, 2026 · 1 revision

title: endoflife.date type: tool created: 2026-05-26 last_updated: 2026-05-26 related: ["radar/tools/Syft", "radar/tools/Steampipe", "radar/techniques/SecureByDesign"] sources: ["https://endoflife.date/"] radar_quadrant: Tools radar_ring: Assess radar_position: inner

endoflife.date

A community-maintained reference site and API aggregating end-of-life (EOL) and release schedules for 300+ software products, frameworks, operating systems, and cloud services. Provides a single consistent source for EOL dates that are otherwise scattered across vendor documentation pages.

The Problem

Every dependency in a production system has an EOL date after which security patches stop. Tracking this across a full stack — Python runtime, OS, database, framework, cloud runtime, container base image — requires monitoring dozens of vendor pages with inconsistent formats. Teams typically discover EOL dates late, during a CVE triage or compliance audit.

What It Provides

endoflife.date aggregates EOL schedules into a uniform format. For each product and version, it shows:

  • Release date
  • End of active support
  • End of security support (EOL date)
  • Extended support windows (where applicable)
  • Latest release in the cycle

Coverage includes: Python, Node.js, Go, Ruby, Java LTS, Ubuntu, Debian, RHEL, PostgreSQL, MySQL, Redis, MongoDB, Nginx, AWS Lambda runtimes, Kubernetes, Django, Rails, and 280+ others.

API

A REST API (https://endoflife.date/api/{product}/{version}.json) returns structured JSON for any product/version combination. This enables programmatic use: CI checks that flag dependencies approaching EOL, inventory dashboards that show the EOL status of every component in a fleet, or scripts that compare a running system's versions against EOL data.

Radar Assessment

endoflife.date sits in the Assess ring of the Tools quadrant, at inner position. First studied via endoflife.date (2024-11-07). Dependency lifecycle management is a security and compliance hygiene practice that lacks good tooling — teams track EOL dates manually or not at all. endoflife.date solves the data aggregation problem with a free, open API. The REST API makes it composable with Steampipe, CI pipelines, or any inventory tooling. Complements syft (SBOM generation) for a complete dependency lifecycle view: syft identifies what is installed, endoflife.date identifies when it expires. Remaining gate before Trial is an automated check querying the API against at least one real system's dependency inventory.

Clone this wiki locally