endoflife.date Lifecycle Scraper

endoflife.date Lifecycle Scraper

Scrape endoflife.date for product lifecycle data, release cycles, and EOL dates across hundreds of products. Every cycle comes with its release date, support status, and LTS flag. No API key. Export to CSV, JSON, Excel, or XML.

endoflife.date tracks end-of-life and support dates for hundreds of software products, but there is no official API and manual checks do not scale. This Actor reads the public product pages directly, filters by LTS or support status, and returns each release cycle in one fixed schema.

Who uses it	What they scrape endoflife.date for
IT asset managers	Which software versions in the estate are approaching end of support
Security teams	Which products have release cycles that are no longer receiving security patches
Procurement teams	Which vendors have frequent LTS releases that affect renewal timing
DevOps engineers	Which runtime versions to pin in CI pipelines to stay on supported releases

What it does

This Actor collects product lifecycle data from endoflife.date by product slug or across all products, and returns each release cycle as a flat row.

• 🎯 Product filter: scrape one product by slug, for example nodejs, python, or ubuntu, or leave blank to collect all products.
• 🛡️ LTS only: limit results to release cycles marked as long-term support.
• ✅ Currently supported only: return only cycles still receiving active support.
• 🔢 Maximum products: cap how many products to collect per run, from 1 to 1,000,000.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with endoflife.date data

📅 Build an upgrade calendar.

An IT asset manager scrapes all products, filters to currently supported only, and maps release dates to plan upgrades before support ends.

🔒 Audit security exposure.

A security team scrapes a watchlist of product slugs, keeps only cycles past end of life, and flags versions that no longer receive patches.

🧪 Pin CI runtimes.

A DevOps engineer scrapes nodejs and python, filters to LTS only, and pins the newest supported release in pipeline images.

📊 Compare vendor cadence.

A procurement analyst scrapes all products, exports to CSV, and compares release frequency and LTS length across vendors before renewal.

Why choose this scraper

	What you get
No API key	Reads public endoflife.date pages directly, no registration or token.
One fixed schema	Every cycle returns the same flat fields, ready for joins and dashboards.
Filter before export	LTS and supported-only flags cut noise before the dataset is written.
All products or one	Scrape the whole catalog or a single product slug in the same run.

How it compares

This Actor reads the same public endoflife.date pages as the other scrapers, but its input schema is built around product slugs and LTS or support filters rather than watchlists or change records.

Feature	ParseForge	Product End-of-Life & Lifecycle Scraper	Software EOL & Support Monitor
Scrape all products	Yes	Not listed	Not listed
Filter by product slug	Yes	Not listed	Not listed
LTS only filter	Yes	Not listed	Not listed
Currently supported only filter	Yes	Not listed	Not listed
No API key required	Yes	Yes	Not listed
Persistent snapshots and change records	Not listed	Not listed	Yes

Configure the run

Drive the Actor from a product slug or leave it blank to scrape all products, and filters run as each cycle is read so only matches reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

{
 "maxItems": 10
}

A larger pull:

{
 "maxItems": 200
}

Pricing

Pay-per-result: $0.0085 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$0.85
1,000 results	$8.50
10,000 results	$85.00

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the endoflife.date Lifecycle Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to endoflife.date through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/endoflife-date-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check the Product slug. It must match the endoflife.date URL exactly, for example nodejs, python, ubuntu. Also check that LTS only or currently supported only is not filtering out every cycle.

Why did the run stop before my Maximum products?

The Actor stops when it has read all available products or hit the cap, whichever comes first. If you left Product blank, it scrapes the whole catalog up to the cap.

Why are some cycles missing?

If LTS only is on, non-LTS cycles are dropped. If currently supported only is on, cycles past end of support are dropped. Turn both off to get every cycle.

Can I get historical EOL dates?

No. The Actor reads the live pages only. To track changes over time, schedule regular runs and store the snapshots.

Why is the run slow?

Scraping all products with a high Maximum products reads many pages. Lower the cap or set a specific Product slug to speed it up.

FAQ

Question	Answer
Do I need an API key for endoflife.date?	No. The Actor reads the public product pages directly, so there is no registration or token to manage.
Can I scrape one product?	Yes. Set the Product field to a slug like nodejs, python, or ubuntu, and the Actor returns only that product's release cycles.
What does LTS only do?	It filters the results to release cycles marked as long-term support, so you only get the versions with extended support windows.
What does currently supported only do?	It returns only cycles still receiving active support, dropping anything already past its end-of-support date.
How many products can I scrape in one run?	You can set Maximum products from 1 up to 1,000,000. Leave Product blank to scrape the whole catalog up to that cap.
What format is the output?	The Actor returns a flat dataset you can export to CSV, JSON, Excel, or XML from Apify.
Does the Actor store historical data?	No. Each run reads the current endoflife.date pages and returns what is live at that moment. Schedule runs to build your own history.
Can I filter by release date?	The input schema does not include a date filter. Use LTS only or currently supported only, then filter the exported dataset by date.
What if a product slug is wrong?	The Actor will return no rows for that product. Check the slug against endoflife.date, for example nodejs, not node.js.
Is this affiliated with endoflife.date?	No. This is an independent scraper that reads the public pages. endoflife.date is a community-maintained project.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by endoflife.date. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.