EOL intelligence,
where your team already works.

Fail the build before your stack goes end-of-life. Scans your repository for version pins — .nvmrc, .python-version, Gemfile, go.mod, Dockerfile FROM lines, package.json engines, .tool-versions and more — and checks each against the endoflife.ai API. EOL runtimes fail the build with annotations and a job summary; approaching-EOL runtimes warn.

Inline end-of-life warnings as you type. A red underline on any version pin that is EOL, yellow when it's approaching. Hover for the EOL date, days past EOL, and a link to the full risk score card. Supports .nvmrc, .python-version, .ruby-version, .tool-versions, package.json engines, go.mod, Dockerfile, and composer.json.

Install the endoflife.ai integration in Datadog and every product in your estate gets an EOL Risk Score (0 to 100), a days-until-end-of-life metric and a CISA KEV exposure factor, pushed as four metric families (endoflife.risk_score, endoflife.days_until_eol, endoflife.kev_factor_score, endoflife.stack_risk_score). The out-of-the-box EOL Risk Overview dashboard shows what is past end of life and actively exploited, what is approaching its date and which hosts run at-risk software; the monitor templates alert before a deadline, not after. The dates behind it are the same 700+ products endoflife.ai publishes, each with its source and verification timestamp.

Datadog and the Datadog logo are trademarks of Datadog, Inc., used with Datadog’s permission. endoflife.ai is not affiliated with or endorsed by Datadog, Inc.

EOL status for your whole stack on the dashboards your team already watches — no exporter to run. Prometheus scrapes the endoflife.ai metrics endpoint directly; one scrape job listing your stack as slug:version pairs is the entire setup. Stat row, per-component risk scores colored by band, sortable inventory, days-until-EOL trend, and the per-factor score breakdown.

From November 16, 2026 at 00:00 UTC the metrics endpoint needs an API key; the authorization line sends it as a Bearer token (Prometheus 2.26+). Free key, emailed at once.

The Grafana Labs Marks are trademarks of Grafana Labs, and are used with Grafana Labs' permission. We are not affiliated with, endorsed or sponsored by Grafana Labs or its affiliates.

endoflife.ai Lifecycle Intelligence (API and MCP server) is listed in the Red Hat Ecosystem Catalog. We validated the API client, CLI, GitHub Action and MCP server on Red Hat® Enterprise Linux® 9 and 10; the validation is ours, not a certification by Red Hat. Dates for Red Hat Enterprise Linux and Red Hat OpenShift® are read from the product life-cycle data Red Hat publishes, and every date names its source.

Red Hat, Red Hat Enterprise Linux and OpenShift are trademarks of Red Hat, LLC, registered in the United States and other countries. endoflife.ai is not affiliated with or endorsed by Red Hat.

EOL Risk Scores™, days to end of life and CISA KEV exposure for 700+ products as Dynatrace metrics, next to the hosts and services you already monitor. A single-file exporter (Python, no dependencies) pushes four metric keys once a day from our public scores feed; an 11-tile EOL Risk Overview dashboard and a critical-risk alert recipe come with it. One access token with the metrics.ingest scope is the whole setup.

For MSPs on HaloPSA: a daily run reads each asset's operating system and Software tab, matches them to endoflife.ai data for 700+ products and writes twelve fields onto the asset: end of support, end of life, status, the EOL Risk Score™ and grade, the exploited-and-unpatchable flag, and the vendor source with its verified day. Assets past end of life can open a ticket against their customer and site. Plain Node.js on your own schedule; only product names and versions leave your Halo.

HaloPSA and Halo are trademarks of their owner. endoflife.ai is not affiliated with or endorsed by HaloPSA or Halo Service Solutions.

A classic monitoring check for end-of-life exposure: OK while supported, WARNING as end of life approaches, CRITICAL once it's past — with the EOL date, days remaining, and EOL Risk Score™ in the status line and perfdata. Zero dependencies (Python 3 standard library), MIT licensed, Icinga2 command definition included.

Agentless Zabbix 6.0+ template: one HTTP-agent call per hour, then a discovery rule creates per-component items — EOL Risk Score™, lifecycle status, days until EOL, latest release — with triggers for end-of-life, approaching-EOL, and high risk. Merged into the official zabbix/community-templates repository on September 10, 2026 (Applications/Security/template_endoflife_ai).

Give any MCP-compatible AI agent — Claude, Cursor, and the rest — direct, structured access to lifecycle intelligence: EOL dates, support status, EOL Risk Scores™, and the verification record behind every date. Ask "which of these versions dies within 180 days?" and get an answer grounded in verified data, not model memory.

The endoflife.ai MCP server is listed on the Tenable CyberAgents Exchange as an MCP server: end-of-life dates, EOL Risk Scores™, CISA KEV exposure, SBOM audits and edge-device end-of-support status for 700+ products, for any MCP-compatible agent. It is the same server described above; the listing points to the same endpoint.

endoflife.ai is not affiliated with or endorsed by Tenable.

Free, live end-of-life status badges for your README, powered by Shields.io endpoint badges. Shows a product's EOL status or its EOL Risk Score™, regenerated with every endoflife.ai build.