Discofork
Repository brief

coreybutler/nvm-windows

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T12:59:44.958Z
3mo ago

coreybutler/nvm-windows

`coreybutler/nvm-windows` is a popular Windows-only Node.js version manager. It is active, not archived, and appears to be in a transition period toward a successor project called Author/Runtime, with recent README notices distinguishing the latest v1.2.x line from the stable v1.1.12 release.

GitHub
Loading tags...
Stars45,722
Forks3,775
Default branchmaster
Last pushed2026-03-08T05:10:07Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose upstream unless you specifically want a near-vanilla fork to customize yourself. This fork does not show added capabilities and is slightly behind upstream, so it is better suited to users who value a simple mirror over new functionality.

Prefer upstream. This fork shows no product differentiation, is materially behind, and does not appear to be maintained as an alternative distribution.

Choose this fork if you want a conservative nvm-windows variant with targeted install/build fixes. Stay with upstream if you want the latest release-line changes and broader project direction.

Adopt this fork only if you need an untouched historical snapshot. For normal use, upstream is the better choice because this fork is 61 commits behind and shows no fork-specific improvements.

Do not adopt this fork for normal use. Choose upstream unless you specifically want an untouched historical snapshot of `nvm-windows`.

Choose this fork only if Nano Server support or its custom issue workflow matters more than staying current with upstream. For most users, upstream is the safer choice because this fork looks stale and only lightly modified.

This fork adds no visible functionality and is materially behind upstream, so adopters should prefer upstream unless they specifically need an unmodified historical snapshot.

Prefer upstream unless you specifically need a frozen, minimally changed baseline; this fork adds no visible features and lags recent upstream maintenance.

Choose this fork if your main blocker is lack of admin rights on Windows and you want a minimal, targeted workaround. Choose upstream instead if you want the current maintenance line, newer fixes, and the broader transition path toward Runtime.

Choose this fork only if the junction workaround solves a concrete permission problem for your Windows setup. Otherwise, upstream is the better default because it is much more active and carries newer release-track changes.