Complete end-of-life dates, support windows, and security status for all Weakforced versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.0 | 2.0.1 | Dec 11, 2018 | Nov 25, 2019 | 2357 days past EOL | EOL |
| 2.2 | 2.2.2 | Nov 7, 2019 | Aug 5, 2020 | 2103 days past EOL | EOL |
| 2.4 | 2.4.1 | Aug 5, 2020 | Nov 24, 2021 | 1627 days past EOL | EOL |
| 2.6 | 2.6.2 | Nov 24, 2021 | Dec 5, 2022 | 1251 days past EOL | EOL |
| 2.8 | 2.8.0 | Dec 5, 2022 | Dec 20, 2023 | 871 days past EOL | EOL |
| 2.10 | 2.10.3 | Dec 5, 2023 | Aug 23, 2024 | 624 days past EOL | EOL |
| 2.12 | 2.12.1 | Aug 23, 2024 | Aug 20, 2025 | 262 days past EOL | EOL |
| 3.0 | 3.0.1 | Aug 20, 2025 | Already EOL | Supported | Active |
When a Weakforced 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 Weakforced 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 →