Complete end-of-life dates, support windows, and security status for all Cachet versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.0 | Jun 19, 2015 | Aug 1, 2015 | 3934 days past EOL | EOL |
| 1.1 | 1.1.1 | Aug 1, 2015 | Aug 19, 2015 | 3916 days past EOL | EOL |
| 1.2 | 1.2.1 | Aug 18, 2015 | Nov 22, 2015 | 3821 days past EOL | EOL |
| 2.0 | 2.0.4 | Nov 22, 2015 | Feb 6, 2016 | 3745 days past EOL | EOL |
| 2.1 | 2.1.2 | Feb 6, 2016 | Mar 27, 2016 | 3695 days past EOL | EOL |
| 2.2 | 2.2.4 | Mar 27, 2016 | Jun 27, 2016 | 3603 days past EOL | EOL |
| 2.3 | 2.3.18 | Jun 27, 2016 | Oct 27, 2023 | 925 days past EOL | EOL |
| 2.4 | 2.4.1 | Oct 27, 2023 | Already EOL | Supported | Active |
When a Cachet version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Cachet should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →