nvm · Lifecycle Status

nvm End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all nvm versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

nvm 0.40.5 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
0.40.5
0.40 series
Next EOL
None upcoming
Active Versions
1
of 40 total
EOL Versions
39
no longer patched
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 →
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20112012201320142015201620172018201920202021202220232024202520260.10.20.30.40.50.60.70.80.90.100.110.120.130.140.150.160.170.180.190.200.210.220.230.240.250.260.270.280.290.300.310.320.330.340.350.360.370.380.390.40TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
0.1 0.1.0 Feb 25, 2011 Nov 29, 2013 4589 days past EOL EOL
0.2 0.2.0 Nov 29, 2013 Mar 21, 2014 4477 days past EOL EOL
0.3 0.3.0 Mar 21, 2014 Mar 27, 2014 4471 days past EOL EOL
0.4 0.4.0 Mar 27, 2014 Apr 20, 2014 4447 days past EOL EOL
0.5 0.5.1 Apr 20, 2014 May 4, 2014 4433 days past EOL EOL
0.6 0.6.1 May 4, 2014 May 8, 2014 4429 days past EOL EOL
0.7 0.7.0 May 8, 2014 Jun 20, 2014 4386 days past EOL EOL
0.8 0.8.0 Jun 20, 2014 Jun 26, 2014 4380 days past EOL EOL
0.9 0.9.0 Jun 26, 2014 Jun 27, 2014 4379 days past EOL EOL
0.10 0.10.0 Jun 27, 2014 Jul 15, 2014 4361 days past EOL EOL
0.11 0.11.2 Jul 15, 2014 Jul 23, 2014 4353 days past EOL EOL
0.12 0.12.2 Jul 23, 2014 Aug 3, 2014 4342 days past EOL EOL
0.13 0.13.1 Aug 3, 2014 Aug 27, 2014 4318 days past EOL EOL
0.14 0.14.0 Aug 27, 2014 Sep 3, 2014 4311 days past EOL EOL
0.15 0.15.0 Sep 3, 2014 Sep 11, 2014 4303 days past EOL EOL
0.16 0.16.1 Sep 11, 2014 Sep 24, 2014 4290 days past EOL EOL
0.17 0.17.3 Sep 24, 2014 Nov 5, 2014 4248 days past EOL EOL
0.18 0.18.0 Nov 5, 2014 Nov 23, 2014 4230 days past EOL EOL
0.19 0.19.0 Nov 23, 2014 Nov 29, 2014 4224 days past EOL EOL
0.20 0.20.0 Nov 29, 2014 Dec 22, 2014 4201 days past EOL EOL
0.21 0.21.0 Dec 22, 2014 Dec 27, 2014 4196 days past EOL EOL
0.22 0.22.2 Dec 27, 2014 Jan 20, 2015 4172 days past EOL EOL
0.23 0.23.3 Jan 20, 2015 Mar 6, 2015 4127 days past EOL EOL
0.24 0.24.2 Mar 6, 2015 Apr 26, 2015 4076 days past EOL EOL
0.25 0.25.4 Apr 26, 2015 Aug 14, 2015 3966 days past EOL EOL
0.26 0.26.1 Aug 14, 2015 Sep 26, 2015 3923 days past EOL EOL
0.27 0.27.1 Sep 26, 2015 Oct 2, 2015 3917 days past EOL EOL
0.28 0.28.0 Oct 2, 2015 Oct 9, 2015 3910 days past EOL EOL
0.29 0.29.0 Oct 9, 2015 Dec 28, 2015 3830 days past EOL EOL
0.30 0.30.2 Dec 28, 2015 Feb 15, 2016 3781 days past EOL EOL
0.31 0.31.7 Feb 15, 2016 Sep 16, 2016 3567 days past EOL EOL
0.32 0.32.1 Sep 16, 2016 Dec 30, 2016 3462 days past EOL EOL
0.33 0.33.11 Dec 30, 2016 Jan 8, 2019 2723 days past EOL EOL
0.34 0.34.0 Jan 8, 2019 Oct 2, 2019 2456 days past EOL EOL
0.35 0.35.3 Oct 2, 2019 Sep 24, 2020 2098 days past EOL EOL
0.36 0.36.0 Sep 24, 2020 Nov 6, 2020 2055 days past EOL EOL
0.37 0.37.2 Nov 6, 2020 Mar 29, 2021 1912 days past EOL EOL
0.38 0.38.0 Mar 29, 2021 Oct 7, 2021 1720 days past EOL EOL
0.39 0.39.7 Oct 7, 2021 Jul 30, 2024 693 days past EOL EOL
0.40 0.40.5 Jul 30, 2024 TBD Supported Active

What does nvm end of life mean for your organization?

When a version of nvm 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 nvm 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.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL nvm versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Need Extended Support?

We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.

Contact Us →
Frequently Asked Questions
What is the end-of-life date for nvm?
See the full table above for all nvm version EOL dates.
When is the nvm support end date?
Each nvm version has its own support end date — see the table above for every version's date.
What is the latest supported version of nvm?
The latest active version of nvm is 0.40.5. Always verify against the table above as support windows can change.
What happens when nvm reaches end of life?
When nvm reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of nvm?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL nvm versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →