Complete end-of-life dates, support windows, and security status for all Deno versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.46.3 | Apr 13, 2020 | Oct 9, 2024 | 577 days past EOL | EOL |
| 2.0 | 2.0.6 | Oct 8, 2024 | Nov 21, 2024 | 534 days past EOL | EOL |
| 2.1 LTS | 2.1.14 | Nov 21, 2024 | Apr 30, 2025 | 374 days past EOL | EOL |
| 2.2 LTS | 2.2.15 | Feb 18, 2025 | Oct 31, 2025 | 190 days past EOL | EOL |
| 2.3 | 2.3.7 | Apr 30, 2025 | Jul 1, 2025 | 312 days past EOL | EOL |
| 2.4 | 2.4.5 | Jul 1, 2025 | Sep 10, 2025 | 241 days past EOL | EOL |
| 2.5 LTS | 2.5.7 | Sep 10, 2025 | Apr 30, 2026 | 9 days past EOL | EOL |
| 2.6 | 2.6.10 | Dec 10, 2025 | Feb 25, 2026 | 73 days past EOL | EOL |
| 2.7 | 2.7.14 | Feb 25, 2026 | Already EOL | Supported | Active |
When a Deno 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 Deno 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 →