Gleam End of Life Dates
other
Developers rely on a variety of tools to streamline their workflow, and one such tool is Gleam, which has been around to help track end-of-life dates, supported versions, and security patch timelines. Created to address the issue of staying up-to-date with the latest versions and security patches, Gleam has become an essential resource for many. The maintainers of Gleam work tirelessly to ensure that the information provided is accurate and reliable, allowing developers to plan their upgrades and migrations with confidence. By using Gleam, developers can ensure that their projects are always running on supported and secure versions.
The end-of-life landscape for Gleam is quite extensive, with a total of 18 versions, out of which 17 have already reached their end-of-life. This leaves only one active version, which is the latest stable version 1.17.0. The most recent version to reach its end-of-life was version 1.16, which occurred on 2026-06-02. Since there is only one active version, there is no next end-of-life date announced, giving developers a sense of stability and reliability. This information is crucial for developers to plan their projects and ensure that they are not using outdated or unsupported versions.
The security picture for Gleam is extremely positive, with a total of 0 CVEs tracked and 0 critical CVEs. This means that there are no known security vulnerabilities in any of the Gleam versions. As a result, there is no most affected version, and the KEV status is not applicable. With such a clean security record, developers can use Gleam with confidence, knowing that their projects are secure and up-to-date. To stay on top of their game, developers should continue to monitor the Gleam website for any updates and ensure that they are always using the latest stable version, which is currently 1.17.0.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 1.17 | Jun 2, 2026 | — | No | — | 1.17.0 | — | Active | |
| 1.16 | Apr 24, 2026 | — | Jun 2, 2026 | 52d ago | 1.16.0 | — | EOL | |
| 1.15 | Mar 16, 2026 | — | Apr 24, 2026 | 91d ago | 1.15.4 | — | EOL | |
| 1.14 | Dec 25, 2025 | — | Mar 16, 2026 | 130d ago | 1.14.0 | — | EOL | |
| 1.13 | Oct 19, 2025 | — | Dec 25, 2025 | 211d ago | 1.13.0 | — | EOL | |
| 1.12 | Aug 5, 2025 | — | Oct 19, 2025 | 278d ago | 1.12.0 | — | EOL | |
| 1.11 | Jun 2, 2025 | — | Aug 5, 2025 | 353d ago | 1.11.1 | — | EOL | |
| 1.10 | Apr 14, 2025 | — | Jun 2, 2025 | 417d ago | 1.10.0 | — | EOL | |
| 1.9 | Mar 8, 2025 | — | Apr 14, 2025 | 466d ago | 1.9.1 | — | EOL | |
| 1.8 | Feb 7, 2025 | — | Mar 8, 2025 | 503d ago | 1.8.1 | — | EOL | |
| 1.7 | Jan 4, 2025 | — | Feb 7, 2025 | 532d ago | 1.7.0 | — | EOL | |
| 1.6 | Nov 18, 2024 | — | Jan 4, 2025 | 566d ago | 1.6.3 | — | EOL | |
| 1.5 | Sep 19, 2024 | — | Nov 18, 2024 | 613d ago | 1.5.1 | — | EOL | |
| 1.4 | Aug 2, 2024 | — | Sep 19, 2024 | 673d ago | 1.4.1 | — | EOL | |
| 1.3 | Jul 9, 2024 | — | Aug 2, 2024 | 721d ago | 1.3.2 | — | EOL | |
| 1.2 | May 27, 2024 | — | Jul 9, 2024 | 745d ago | 1.2.1 | — | EOL | |
| 1.1 | Apr 16, 2024 | — | May 27, 2024 | 788d ago | 1.1.1 | — | EOL | |
| 1.0 | Mar 4, 2024 | — | Apr 16, 2024 | 829d ago | 1.0.0 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
