Nvm 0.30 · Version Status
Nvm 0.30 End of Life Date
Nvm 0.30 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Nvm 0.30 is past end of life. This version no longer receives security patches. 3736 days past EOL — migrate to a supported version immediately.
EOL Date
Feb 15, 2016
3736 days past EOL
Latest Release
0.30.2
Standard release
Release Date
Dec 28, 2015
Nvm 0.30 series
| Version | Latest | EOL Date | Status |
|---|
| 0.1 |
0.1.0 |
Nov 29, 2013 |
EOL |
| 0.2 |
0.2.0 |
Mar 21, 2014 |
EOL |
| 0.3 |
0.3.0 |
Mar 27, 2014 |
EOL |
| 0.4 |
0.4.0 |
Apr 20, 2014 |
EOL |
| 0.5 |
0.5.1 |
May 4, 2014 |
EOL |
| 0.6 |
0.6.1 |
May 8, 2014 |
EOL |
| 0.7 |
0.7.0 |
Jun 20, 2014 |
EOL |
| 0.8 |
0.8.0 |
Jun 26, 2014 |
EOL |
What does Nvm 0.30 end of life mean?
When Nvm 0.30 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Nvm 0.30 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Nvm 0.40 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Nvm 0.30 reach end of life?
Nvm 0.30 reached end of life on February 15, 2016. This version is no longer receiving security patches.
Is Nvm 0.30 still supported?
No. Nvm 0.30 reached end of life on February 15, 2016 and is no longer receiving security patches.
What should I upgrade to from Nvm 0.30?
The recommended upgrade from Nvm 0.30 is
Nvm 0.40 — the latest actively supported version. Check the
Nvm full timeline for all supported versions.
What are the security risks of running Nvm 0.30 past EOL?
When Nvm 0.30 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Nvm should migrate immediately or implement compensating controls.