HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
endoflife-date
endoflife.date
Ruby2022–2026
endoflife-date / endoflife.date

endoflife.date

Informative site with EoL dates of everything

3Distinct people
19Mentions
0Explicit recommenders
3.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Informative site with EoL dates of everything

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 5:04:15 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year19 dated mentions

Observed mentions: 2022-03-01 05:15:35 UTC to 2026-04-11 07:02:38 UTC.

0369122022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC11011
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

What Hacker News says

11 sources
Yes, we have an open issue for such timelines (https://github.com/endoflife-date/endoflife.date/issues/2148). Your comment has given me the idea to implement it on our "tag" pages, so you could see the timeline for all java-runtimes in one place for eg. Generating pages isn't hard for us. We maintain it in our frontmatter/yaml (See https://github.com/endoflife-date/endoflife.date/blob/master... for example). The release-data repo is for tracking new releases of upstream products so we can patch the latest version automatically, and get notified of new major releases that are missing in our tables. release-data is a much smaller subset of our data, and doesn't include the critical EOL data.
In End of Life of Technologies and Devices
> where you can see overlapped timelines when support ended I tried to generate a visual timeline for a given page (https://github.com/endoflife-date/endoflife.date/pull/2859, has some screenshots), but it was limited to a single page (so you'd only see nokia devices at once for eg). It turned out that it is too hard to generate clear charts with vague data. We often only know whether is device is supported or not (true/false, see comments about samsung below in this thread), and don't have clear release dates. I'll get to it someday (PRs welcome), but it might not work for the usecase we want (picking phones) because data on mobiles is very vague. repairability score -> sounds interesting, will file an issue and see. The hard part is that there's no clear identifiers for devices (SWID/CPE are just not good enough) for us to track this ki
Read the rest
nd of data from elsewhere easily.
In End of Life of Technologies and Devices
Thank you for creating this. We keep track of EOL dates in our internal wiki with links to various websites. Would be nice to reduce the scatter and just link to this site! Would you accept Pull Requests that add server hardware EOS and EOL dates? They are especially hard to find and it would be great to have them in there as well! Edit: I should have taken a look at open issues first, it seems there is tracking issue for network equipment so I guess adding server hardware is certainly not off the table (https://github.com/endoflife-date/endoflife.date/issues/1387).
In End of Life of Technologies and Devices
We have an open issue for a timeline view: https://github.com/endoflife-date/endoflife.date/issues/2148 Second is very subjective. If there's onething that I've learnt over the years working on this - it is that the definition of "support" is very fuzzy. You can't even compare what "LTS" means between different stacks/products, so it is hard to objectively rate anything. It still might be worth doing some analysis and publishing as a blog post though, but i'm not sure if it can be automatically calculated.
In End of Life of Technologies and Devices
1. We already have a calendar feed that you can subscribe to, for every product that will warn you accordingly. 2. We have an API (endoflife.date/api) and a upcoming v1 API (https://github.com/endoflife-date/endoflife.date/pull/2080) to let everyone use our data. 3. there's already a ton of companies/products that use the api/dataset (https://github.com/endoflife-date/endoflife.date/wiki/Known-...) We plan to launch some services (https://github.com/endoflife-date/endoflife.date/issues/2108), but it will still be free. We treat it as a community-built-semantic-wiki. Feedback is welcome.
In End of Life of Technologies and Devices
Currently none, but that's mostly because we've worked hard to keep it that way. I publish finance updates on a GitHub Discussion (https://github.com/endoflife-date/endoflife.date/discussions...). We used to pay $9/mo for Netlify Analytics but didn't find it helpful. We're looking to join OpenEoX.org to standardize EoL information publication, but that requires a lot more funds (https://github.com/endoflife-date/endoflife.date/discussions...). We also have a pretty long roadmap (https://github.com/endoflife-date/endoflife.date/issues/2108) that focuses on integrating better with the sbom ecosystem (We want to make an API that does SBOM->EOL alerts for eg). Such projects require a lot of development effort, and we'd like to be able to sponsor it on our own (via grants/donations).
In End of Life of Technologies and Devices
endoflife.date: https://endoflife.date Created it because I was frustrated having to lookup information on multiple sites, and having to dig deep and read through terribly written support policies. No Ads, no tracking, all hosted cheaply on Netlify OSS Plan. Now at 100+ contributors, with 3-5 maintainers on the project. We have a long roadmap for the next year[0]. A contributor wrote a EOL Scanner that is based on a fork of grype[1]. [0]: https://github.com/endoflife-date/endoflife.date/issues/2108 [1]: https://github.com/noqcks/xeol
In Ask HN: Those making $0/month or less on side projects – Show and tell

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.