Deno End of Life Dates
other
Deno is a runtime for JavaScript, TypeScript, and WebAssembly, built on the V8 JavaScript engine and the Rust programming language, providing a secure and efficient environment for developers to run their code. Created by Ryan Dahl, the founder of Node.js, and Bert Belder, Deno aims to address the security and performance concerns that have plagued its predecessor. Since its inception, Deno has gained popularity among developers due to its ability to provide a more robust and reliable alternative to traditional runtimes. The project is maintained by its core team, who continuously work to improve and expand its capabilities, making it an attractive choice for developers looking for a modern and secure runtime.
The end-of-life landscape for Deno is relatively straightforward, with a total of 10 versions released so far, out of which 9 have already reached their end-of-life. The latest stable version, 2.8.2, is the only active version currently available, with no announced end-of-life date. The most recent version to reach its end-of-life was version 2.7, which was deprecated on 2026-05-22. This clear versioning and maintenance strategy allows developers to plan and manage their projects with confidence, knowing that they can rely on the latest version of Deno for their development needs.
From a security perspective, Deno has a clean slate, with no known CVEs tracked to date. This is a significant advantage for developers, as it eliminates the risk of critical vulnerabilities that could compromise the security of their applications. With zero critical CVEs, Deno provides a secure foundation for building and deploying applications. As a result, developers can focus on writing code without worrying about underlying security issues. Given the absence of any known security vulnerabilities, developers can confidently use Deno for their projects, and the lack of any pending end-of-life dates for the current version means they can plan for the long-term without concerns about potential security risks.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 2.9 | Jun 25, 2026 | — | No | — | 2.9.4 | — | Active | |
| 2.8 | May 22, 2026 | — | Jun 25, 2026 | 29d ago | 2.8.3 | — | EOL | |
| 2.7 | Feb 25, 2026 | — | May 22, 2026 | 63d ago | 2.7.14 | — | EOL | |
| 2.6 | Dec 10, 2025 | — | Feb 25, 2026 | 149d ago | 2.6.10 | — | EOL | |
| 2.5 LTS | Sep 10, 2025 | — | Apr 30, 2026 | 85d ago | 2.5.7 | — | EOL | |
| 2.4 | Jul 1, 2025 | — | Sep 10, 2025 | 317d ago | 2.4.5 | — | EOL | |
| 2.3 | Apr 30, 2025 | — | Jul 1, 2025 | 388d ago | 2.3.7 | — | EOL | |
| 2.2 LTS | Feb 18, 2025 | — | Oct 31, 2025 | 266d ago | 2.2.15 | — | EOL | |
| 2.1 LTS | Nov 21, 2024 | — | Apr 30, 2025 | 450d ago | 2.1.14 | — | EOL | |
| 2.0 | Oct 8, 2024 | — | Nov 21, 2024 | 610d ago | 2.0.6 | — | EOL | |
| 1 | Apr 13, 2020 | — | Oct 9, 2024 | 653d ago | 1.46.3 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
