Deno 1 · Version Status

Deno 1 End of Life Date

Deno 1 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

Deno 1 is past end of life. This version no longer receives security patches. 714 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 9, 2024
714 days past EOL
Latest Release
1.46.3
Standard release
Release Date
Apr 13, 2020
Deno 1 series
Lifecycle detail

Deno 1 was released on April 13, 2020 and support ended on October 9, 2024 — a supported lifespan of 4 years and 6 months, longer than the 3 months median for Deno releases. It was not an LTS release; Deno reserves longer patch windows for its LTS versions. The last patch it will ever receive is 1.46.3, published September 4, 2024 — 35 days before support ended. It has been without security patches for 2 years. 9 newer Deno releases have shipped since.

All Deno versions Deno 2.0 →
45 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
35/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
Recommended upgrade path
Deno 2.9
Latest release: 2.9.7 · EOL: Supported
View full Deno timeline →
Extended Support
Extended Deno 1 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Deno Versions
VersionLatestEOL DateStatus
1 1.46.3 Oct 9, 2024 EOL
2.0 2.0.6 Nov 21, 2024 EOL
2.1 LTS 2.1.14 Apr 30, 2025 EOL
2.2 LTS 2.2.15 Oct 31, 2025 EOL
2.3 2.3.7 Jul 1, 2025 EOL
2.4 2.4.5 Sep 10, 2025 EOL
2.5 LTS 2.5.7 Apr 30, 2026 EOL
2.6 2.6.10 Feb 25, 2026 EOL

What does Deno 1 end of life mean?

When Deno 1 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Deno 1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Deno 2.9 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Deno 1 reach end of life?
Deno 1 reached end of life on October 9, 2024. This version is no longer receiving security patches.
Is Deno 1 still supported?
No. Deno 1 reached end of life on October 9, 2024 and is no longer receiving security patches.
What should I upgrade to from Deno 1?
The recommended upgrade from Deno 1 is Deno 2.9 — the latest actively supported version. Check the Deno full timeline for all supported versions.
What are the security risks of running Deno 1 past EOL?
When Deno 1 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Deno should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →