endoflife.ai — a companion platform built on top of endoflife.date

[endoflife-ai]

Hi everyone,

I wanted to introduce endoflife.ai to this community since
it's built directly on top of the endoflife.date API and
data — you're a core part of what makes it work.

What I built:

EOL Checker — AI-enriched lookup that surfaces CVE blind
spot warnings for products past their support window. Uses
the endoflife.date API as its primary data source.

Product Index — A browsable, filterable index of 454+
products pulling live from your API. Searchable by category,
status, and days remaining.

Stack Scanner — Upload a requirements.txt, package.json,
Gemfile, or composer.json and get a full EOL report for your
entire dependency tree. Also powered by your API.

Resource Hub — Research articles on EOL risk, CVE blind
spots, enterprise migration guides, and hardware EOSL.

The site is free, no account required, and privacy-first —
all scanning runs in the browser.

I wanted to share it here first because this community
deserves credit for the data foundation that makes it
possible. Happy to answer questions, take feedback, and
discuss any ways we could collaborate or cross-reference
each other.

https://endoflife.ai

— Scott, Founder

[captn3m0]

Looks neat. The reason we do not have a scanner API ourselves is that it is a very hard problem with lots of nuances. And I don't think these are getting considered here. For eg, you aren't parsing Debian version numbers, and thus report django==1:1 as active.

I'd appreciate contributions back upstream from your learnings. We have a few other companies building on top - xeol.io was the biggest one, but it got bought by HeroDevs and is now an internal dataset (https://www.herodevs.com/eol-dataset/overview). There's a few more in our list of Known Users, I'll add you there as well.

[captn3m0]

Oh, and I'd suggest changing your copy from "endoflife.ai is the authoritative reference for software lifecycle dates".

[endoflife-ai]

Just pushed the fix for the Debian epoch parsing —
version strings like 1:4.2 now strip the epoch prefix
correctly before matching.

Also updated the site copy to properly credit
endoflife.date as the data foundation. Really appreciate
the feedback.

[endoflife-ai]

Thanks for the feedback — really appreciated. You’re right on both counts. I’ve updated the copy to remove the “authoritative reference” claim and now credit endoflife.date as the source. The Debian epoch parsing bug is on my radar — I’ll get that fixed and will look to contribute any useful learnings back upstream. Happy to be added to the Known Users list, and thanks for building such a solid foundation to build on.

…

On Sat, May 9, 2026 at 3:30 AM Nemo ***@***.***> wrote: Oh, and I'd suggest changing your copy from "endoflife.ai is the authoritative reference for software lifecycle dates". — Reply to this email directly, view it on GitHub <#10064 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CDLZ2UYZL3JBGCT5ITI7LO34Z33FFAVCNFSM6AAAAACYW72REWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMOBWGEYTINI> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: <endoflife-date/endoflife.date/repo-discussions/10064/comments/16861145@ github.com>