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.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0.1 | 0.1.0 | Feb 25, 2011 | Nov 29, 2013 | 4636 days past EOL | EOL |
| 0.2 | 0.2.0 | Nov 29, 2013 | Mar 21, 2014 | 4524 days past EOL | EOL |
| 0.3 | 0.3.0 | Mar 21, 2014 | Mar 27, 2014 | 4518 days past EOL | EOL |
| 0.4 | 0.4.0 | Mar 27, 2014 | Apr 20, 2014 | 4494 days past EOL | EOL |
| 0.5 | 0.5.1 | Apr 20, 2014 | May 4, 2014 | 4480 days past EOL | EOL |
| 0.6 | 0.6.1 | May 4, 2014 | May 8, 2014 | 4476 days past EOL | EOL |
| 0.7 | 0.7.0 | May 8, 2014 | Jun 20, 2014 | 4433 days past EOL | EOL |
| 0.8 | 0.8.0 | Jun 20, 2014 | Jun 26, 2014 | 4427 days past EOL | EOL |
| 0.9 | 0.9.0 | Jun 26, 2014 | Jun 27, 2014 | 4426 days past EOL | EOL |
| 0.10 | 0.10.0 | Jun 27, 2014 | Jul 15, 2014 | 4408 days past EOL | EOL |
| 0.11 | 0.11.2 | Jul 15, 2014 | Jul 23, 2014 | 4400 days past EOL | EOL |
| 0.12 | 0.12.2 | Jul 23, 2014 | Aug 3, 2014 | 4389 days past EOL | EOL |
| 0.13 | 0.13.1 | Aug 3, 2014 | Aug 27, 2014 | 4365 days past EOL | EOL |
| 0.14 | 0.14.0 | Aug 27, 2014 | Sep 3, 2014 | 4358 days past EOL | EOL |
| 0.15 | 0.15.0 | Sep 3, 2014 | Sep 11, 2014 | 4350 days past EOL | EOL |
| 0.16 | 0.16.1 | Sep 11, 2014 | Sep 24, 2014 | 4337 days past EOL | EOL |
| 0.17 | 0.17.3 | Sep 24, 2014 | Nov 5, 2014 | 4295 days past EOL | EOL |
| 0.18 | 0.18.0 | Nov 5, 2014 | Nov 23, 2014 | 4277 days past EOL | EOL |
| 0.19 | 0.19.0 | Nov 23, 2014 | Nov 29, 2014 | 4271 days past EOL | EOL |
| 0.20 | 0.20.0 | Nov 29, 2014 | Dec 22, 2014 | 4248 days past EOL | EOL |
| 0.21 | 0.21.0 | Dec 22, 2014 | Dec 27, 2014 | 4243 days past EOL | EOL |
| 0.22 | 0.22.2 | Dec 27, 2014 | Jan 20, 2015 | 4219 days past EOL | EOL |
| 0.23 | 0.23.3 | Jan 20, 2015 | Mar 6, 2015 | 4174 days past EOL | EOL |
| 0.24 | 0.24.2 | Mar 6, 2015 | Apr 26, 2015 | 4123 days past EOL | EOL |
| 0.25 | 0.25.4 | Apr 26, 2015 | Aug 14, 2015 | 4013 days past EOL | EOL |
| 0.26 | 0.26.1 | Aug 14, 2015 | Sep 26, 2015 | 3970 days past EOL | EOL |
| 0.27 | 0.27.1 | Sep 26, 2015 | Oct 2, 2015 | 3964 days past EOL | EOL |
| 0.28 | 0.28.0 | Oct 2, 2015 | Oct 9, 2015 | 3957 days past EOL | EOL |
| 0.29 | 0.29.0 | Oct 9, 2015 | Dec 28, 2015 | 3877 days past EOL | EOL |
| 0.30 | 0.30.2 | Dec 28, 2015 | Feb 15, 2016 | 3828 days past EOL | EOL |
| 0.31 | 0.31.7 | Feb 15, 2016 | Sep 16, 2016 | 3614 days past EOL | EOL |
| 0.32 | 0.32.1 | Sep 16, 2016 | Dec 30, 2016 | 3509 days past EOL | EOL |
| 0.33 | 0.33.11 | Dec 30, 2016 | Jan 8, 2019 | 2770 days past EOL | EOL |
| 0.34 | 0.34.0 | Jan 8, 2019 | Oct 2, 2019 | 2503 days past EOL | EOL |
| 0.35 | 0.35.3 | Oct 2, 2019 | Sep 24, 2020 | 2145 days past EOL | EOL |
| 0.36 | 0.36.0 | Sep 24, 2020 | Nov 6, 2020 | 2102 days past EOL | EOL |
| 0.37 | 0.37.2 | Nov 6, 2020 | Mar 29, 2021 | 1959 days past EOL | EOL |
| 0.38 | 0.38.0 | Mar 29, 2021 | Oct 7, 2021 | 1767 days past EOL | EOL |
| 0.39 | 0.39.7 | Oct 7, 2021 | Jul 30, 2024 | 740 days past EOL | EOL |
| 0.40 | 0.40.6 | Jul 30, 2024 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/nvm)
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.
Your options when nvm reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
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.
nvm has 39 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for nvm exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.