nvm-windows/nvm
The Node.js version manager for Windows.
47.9k stars · 3.9k forks · Inno Setup
Caution
Caution: one person wrote most of the recent commits.
Why
- One person wrote 92% of human commits in the last year, so the project depends on them continuing. (source 1, source 2)
What would change this
- A second person takes a substantial share of commits.
Maintenance
CompleteActive
- Human commits, 30 days
- 66
- Human commits, 90 days
- 130
- Human commits, 365 days
- 130
- Bot share of commits, 365 days
- 12%
- Last commit
- Oct 13, 2026 (1 day ago)
- Last human commit
- Oct 13, 2026 (1 day ago)
- Authors, 90 days
- 2
- Last release
- Oct 2, 2026 (12 days ago)
- Median PR merge time
- 2 hours
Responsiveness: of 23 recent issues, 96% got a maintainer reply. Median first response: 7 hours.
Sources: Commits, Releases, Merged pull requests, Issues
People
Complete- Owner
- Organization
- Commits sampled
- 130 since Oct 14, 2025
- Authors for half of commits
- 1
- Authors for 80% of commits
- 1
- Contributors
- 3
Top committers
- coreybutler: 92% of commits
- gbdrummer: 8% of commits
Sources: Commits, Contributors
Stars
CompleteOrganic, confidence high
- 5 stars GitHub has since removed (tracked since Oct 13, 2026).
Anyone can buy stars for any repo; bursts alone don't prove the owner did.
- The star history looks organic.
Sources: How star history is analyzed
Risk
CompleteFlags
No risk flags.
License
- Now
- MIT (OSI-approved)
- A year ago
- Not known
Packages
No published packages found.
Sources: GitHub: nvm-windows/nvm
Badge
Add this to a README to show the current verdict:
[](https://reporadar.ai/nvm-windows/nvm)Earlier verdicts
- Oct 14, 2026: Caution
- Oct 13, 2026: Caution
- Oct 13, 2026: Caution
Computed 16 hours ago · method 2026.10.2