Show HN: Fail CI when your stack runs end-of-life software

eol-check, a GitHub Action published under the endoflife-ai organization, launched on August 20, 2026, as a tool that fails CI pipelines when a project's stack contains end-of-life software, per a Show HN post by author ScottUbiquitous.

The project, hosted at github.com/endoflife-ai/eol-check, is designed to be dropped into existing CI workflows. When triggered, it checks the software components in a stack against end-of-life data and returns a non-zero exit code — failing the build — if any component has passed its support window.

The core problem the tool addresses is that end-of-life software often stays in production unnoticed. Runtimes, frameworks, and operating system images age past their vendor support dates without teams explicitly opting out; eol-check surfaces those gaps at the CI layer, where they can block deploys rather than surface in a security audit after the fact.

The HN submission had 2 points and no comments at time of writing, and no additional sources corroborate details about the tool's implementation, supported ecosystems, or the team behind it. The repository itself is the primary reference for technical specifics.

No funding, company formation, or team details are mentioned in the available sources. What's next for the project — additional ecosystem coverage, a hosted service, or community contributions — is not stated in the submission.