Open-source project
coreybutler/nvm-windows avatar
coreybutler/nvm-windows

NVM for Windows v2: shim mode, directory pinning and a paid Certified Build for managed fleets

A node.js version management utility for Windows. Ironically written in Go.

48,207 stars3,899 forksGoMIT

At a glance

What is it?
NVM for Windows is a Go based Node.js version manager for Windows, now fully rewritten as v2. The Community Edition covers individual developers well; central policy, MSI deployment and audit logging sit only in the commercial Certified Builds.
Who is it for?
NVM for Windows fits Windows developers who switch Node.js versions per project and want that to work without administrator rights. Teams that must restrict versions, deploy through Intune or produce audit logs need the commercial Certified Builds, since the Community Edition does not include those controls.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 4 days ago.
What is it written in?
Mainly Go, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • coreybutler/nvm-windows48,207 ★ · +821
Star history
Repository2026-08-182026-11-15
coreybutler/nvm-windows47.4k48.2k

821 Stars in the last 89 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

It is not nvm, and nvm instructions do not apply

The name causes most of the confusion. The original nvm at nvm-sh/nvm is a completely separate project that runs only on Mac and Linux. NVM for Windows is not a port or a clone of it; it uses a different philosophy and is written in Go, which the project description itself calls ironic. Shell snippets and configuration advice written for nvm will not carry over, so search results that mix the two will mislead you. Use the documentation at docs.nvm-windows.com instead. Microsoft's guide to Node.js on Windows and Google Cloud's Node.js setup page both point Windows users to this project, which is why it is the version manager most Windows tutorials assume. When a tutorial gives commands, check which of the two projects it was written for before running anything.

Shim mode avoids symlinks, link mode uses junctions

Version 2 was fully rewritten and offers two ways to put the active Node.js on your path. Shim mode uses no symlinks and is written in Zig. Link mode is described as zero latency and uses directory junctions, falling back to symlinks. Neither requires mandatory administrator privileges, which matters on locked down corporate laptops where elevation is not available. If one mode conflicts with your tooling, the other is the alternative to try before giving up.

Per-directory pinning installs missing versions on its own

NVM for Windows can switch the Node.js version per directory, a feature it calls pinning. When a pinned version is missing it can install it automatically, and it can also install a user-defined set of default global modules into each new version. User-defined aliases cover names for versions you use often. Installs run in parallel, download smaller 7z archives, extract natively and are cached. For offline machines, downloads can be pointed at a local source for air-gapped use. An example settings file sits in examples/settings.txt in the repository.

Auto-install cuts both ways. Opening a project that pins a version you have never used triggers a download you did not ask for, which is convenient on a home connection and unwelcome on a metered or filtered network. On a machine without internet access, configure the local download source first, or pinned projects will fail to get their Node.js version.

It writes to Windows Event Viewer and the registry

The v2 build integrates with Windows itself rather than living only in a shell. It logs to the Windows Event Viewer, uses the Windows Registry, appears among Windows Apps and sends messages to the Desktop Notification Center. On Microsoft's Project Zenith devices, starting with AMD Ryzen AI Halo hardware, NVM for Windows comes preconfigured, so check whether it is already installed before adding a second copy. More devices from OEM and silicon partners are announced for the coming months, so the number of machines that arrive with it already set up will grow.

Policy control, MSI and audit logs are only in Certified Builds

The free Community Edition has no way for an administrator to lock down what developers install. Those controls belong to commercial Certified Builds: a Windows-protected installation directory, MSI and MST installers, Microsoft Intune deployment, Active Directory and Entra integration, restrictions on Node.js versions or ranges such as LTS only or no end of life versions, proxy support for IWA and WPAD/PAC, and a private Node.js download mirror. Advanced logging with SIEM integration, policy enforcement and trust artifacts such as SBOM, AI-BOM, SLSA provenance, SAST and VEX reports are paid add-ons. An IT team rolling out the Community Edition gets none of this and should read the Choosing a Build guide first.

The v2.1.0 line is still shipping betas days apart

The repository is MIT licensed, not archived, and was last pushed on 2 November 2026. Recent releases are all prereleases: v2.1.0-beta.7 on 31 October 2026, then beta.8 and beta.9 within an hour of each other on 2 November. The README release badges point to v2.0.1 as stable and to the nvm-windows/nvm releases page. Community Edition installers have been code-signed since v2.0.0-hotfix.2, so an unsigned installer claiming to be a recent version is a reason to stop. If you install a beta, expect to update often while the 2.1.0 line settles; if you want fewer surprises, stay on the stable v2 release. The repository holds the Go source under src, a build.js script and an nvm.iss installer definition. Contributors must add a Signed-off-by trailer to every commit:

code
git commit -s

Editorial conclusion

NVM for Windows fits Windows developers who switch Node.js versions per project and want that to work without administrator rights. Teams that must restrict versions, deploy through Intune or produce audit logs need the commercial Certified Builds, since the Community Edition does not include those controls. Before installing, check whether your machine already ships it preconfigured, decide between the stable v2 line and the v2.1.0 betas, and do not follow guides written for the Mac and Linux nvm.

Frequently asked questions

What is NVM for Windows?

NVM for Windows is a Node.js version manager for Windows written in Go. It is a separate project from nvm, which runs only on Mac and Linux.

Is NVM for Windows safe?

NVM for Windows Community Edition installers are code-signed as of v2.0.0-hotfix.2, and the project is MIT licensed. Commercial Certified Builds add trust artifacts such as SBOM and SLSA provenance.

Is NVM for Windows deprecated?

No. NVM for Windows was fully rewritten as version 2, the repository is not archived, and v2.1.0-beta.9 shipped on 2 November 2026.

How to install nvm-windows?

NVM for Windows installers are published on its GitHub releases page and at nvm-windows.com, with setup guidance at docs.nvm-windows.com. On Project Zenith devices it comes preconfigured.

Official sources

  1. Official README
  2. Project repository
  3. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/coreybutler-nvm-windows.svg)](https://hysenlabs.com/projects/coreybutler-nvm-windows)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/coreybutler-nvm-windows.svg)](https://hysenlabs.com/projects/coreybutler-nvm-windows)

Was this useful?