Complete end-of-life dates, support windows, and security status for all Gleam 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 | Mar 4, 2024 | Apr 16, 2024 | 753 days past EOL | EOL |
| 1.1 | 1.1.1 | Apr 16, 2024 | May 27, 2024 | 712 days past EOL | EOL |
| 1.2 | 1.2.1 | May 27, 2024 | Jul 9, 2024 | 669 days past EOL | EOL |
| 1.3 | 1.3.2 | Jul 9, 2024 | Aug 2, 2024 | 645 days past EOL | EOL |
| 1.4 | 1.4.1 | Aug 2, 2024 | Sep 19, 2024 | 597 days past EOL | EOL |
| 1.5 | 1.5.1 | Sep 19, 2024 | Nov 18, 2024 | 537 days past EOL | EOL |
| 1.6 | 1.6.3 | Nov 18, 2024 | Jan 4, 2025 | 490 days past EOL | EOL |
| 1.7 | 1.7.0 | Jan 4, 2025 | Feb 7, 2025 | 456 days past EOL | EOL |
| 1.8 | 1.8.1 | Feb 7, 2025 | Mar 8, 2025 | 427 days past EOL | EOL |
| 1.9 | 1.9.1 | Mar 8, 2025 | Apr 14, 2025 | 390 days past EOL | EOL |
| 1.10 | 1.10.0 | Apr 14, 2025 | Jun 2, 2025 | 341 days past EOL | EOL |
| 1.11 | 1.11.1 | Jun 2, 2025 | Aug 5, 2025 | 277 days past EOL | EOL |
| 1.12 | 1.12.0 | Aug 5, 2025 | Oct 19, 2025 | 202 days past EOL | EOL |
| 1.13 | 1.13.0 | Oct 19, 2025 | Dec 25, 2025 | 135 days past EOL | EOL |
| 1.14 | 1.14.0 | Dec 25, 2025 | Mar 16, 2026 | 54 days past EOL | EOL |
| 1.15 | 1.15.4 | Mar 16, 2026 | Already EOL | Supported | Active |
When a Gleam 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 Gleam 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 →