Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-05 00:07 UTC

coreybutler / nvm-windows

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

Go · Inno SetupMIT★ 47,227 stars⑂ 3,856 forkssince Sep 2014View on GitHub ↗

coreybutler/nvm-windows holds a health index of 50 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (86/100) and lowest on Vitality (35/100). It was last updated 109 days ago. A single contributor accounts for most of its recent work.

50
overall / 100
Moderate

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

50
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 50 is calibrated to 50 on the published index scale (record calibration 2026-08-02).

Ownership

Corey ButlerPersonal account
2,688 followers105 public repossince May 2011@author

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

35Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 109 days ago
3.5/36Commit cadence5/52 weeks with commits
7.6/18Commit volume6 commits in the last year
6/10OpenSSF Scorecard: Maintained0 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 6
Inputs used
commits_last_year6
human_commit_share0.94
days_since_last_push109
active_weeks_last_year5
How it's scored
27/27Ships releases23 releases published
7.2/36Release recencylatest release 580 days ago
12.6/27Release cadencea release every ~302.9 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count23
latest_release_tag1.2.2
releases_from_tagsno
days_since_latest_release580
mean_days_between_releases302.9

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

86Excellent · 17% of overall

Popularity & adoption

100Exceptional
How it's scored
60/60Stars47,227 stars
25/25Forks3,856 forks
14.8/15Watchers461 watchers
Inputs used
forks3,856
stars47,227
watchers461
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges10
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

55Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.5/22.5Commit distributiontop contributor authored 80% of commits
13.5/13.5Contributor breadth74 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled74
top_contributor_share0.798
How it's scored
39.4/42Issue resolution94% of issues closed
16.1/30PR acceptance107/199 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/25 approved changesets -- score normalized to 0
Inputs used
merged_prs107
open_issues59
closed_issues910
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.939
closed_unmerged_prs92
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
24.7/25Owner reach2,688 followers of coreybutler
25/25Track record105 public repos, account ~15 yr old
Inputs used
followers2,688
owner_typeUser
is_verified
owner_logincoreybutler
public_repos105
account_age_days5,570
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

38Weak · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 5 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics11 topics
10/10Wiki
Inputs used
topicsnode, versioning, management, version-manager, windows, nodejs, version, nvm, go, switch, node-version-manager
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

40Weak · 16% of overall
How it's scored
3/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 5 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 1/25 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 5 contributing companies or organizations
0/10Dangerous-Workflowdangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
4.5/7.5Maintained0 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 6
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0.8/7.5Vulnerabilities9 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate2.8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.
How it's scored
26.6/35Direct dependencies free of known advisories1 affected: golang.org/x/sys 0.25.0 (unknown)
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
40/40No advisories left outstandingno advisory has been public longer than 90 days
Inputs used
sourceosv
advisories11
affected_packages2
assessed_packages16
unassessed_packages0
affected_by_severityhigh 1, unknown 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 16 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

52Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
19.3/40Legible commit history34 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.362
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapsrc/go.mod (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checkingGo (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance6 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestssrc/go.mod
dependency_bot_commit_share0.06
How it's scored
45/45Type-checkable codeGo (statically typed)
51.3/55Manageable file sizes1/15 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes62,098
source_files_sampled15
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

47,227GitHub stars
74contributors
6commits, last 12 months
109days since last push
23releases
1bus factor
59open issues
Gopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 3,856 ⇿
0Stars
3,856Forks
3Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

2,5003,0003,5004,0003,856122023-122025-042026-08
Major 0Minor 1Patch 2

Each point covers 3 days.

OpenSSF Scorecard 2.8 / 10
2.8aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-05 00:06 UTC

4Binary-Artifactsbinaries present in source code
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
0CI-Tests0 out of 5 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/25 approved changesets -- score normalized to 0
10Contributorsproject has 5 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
6Maintained0 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 6
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
1Vulnerabilities9 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
Gogithub.com/blang/semverv3.5.1+incompatiblesrc/go.mod
Gogithub.com/coreybutler/go-fsutilv1.2.0src/go.mod
Gogithub.com/coreybutler/go-wherev1.0.2src/go.mod
Gogithub.com/dustin/go-humanizev1.0.1src/go.mod
Gogithub.com/go-toast/toastv0.0.0-20190211030409-01e6764cf0a4src/go.mod
Gogithub.com/ncruces/zenityv0.10.14src/go.mod
Gogithub.com/olekukonko/tablewriterv0.0.5src/go.mod
Gogithub.com/saintfish/chardetv0.0.0-20230101081208-5e3ef4b5456dsrc/go.mod
Gogolang.org/x/sysv0.25.0src/go.mod
All dependencies 16

Full resolved dependency set from the GitHub dependency graph: 9 direct and 7 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Gogithub.com/blang/semver3.5.1+incompatibledirect
Gogithub.com/coreybutler/go-fsutil1.2.0direct
Gogithub.com/coreybutler/go-where1.0.2direct
Gogithub.com/dustin/go-humanize1.0.1direct
Gogithub.com/go-toast/toast0.0.0-20190211030409-01e6764cf0a4direct
Gogithub.com/ncruces/zenity0.10.14direct
Gogithub.com/olekukonko/tablewriter0.0.5direct
Gogithub.com/saintfish/chardet0.0.0-20230101081208-5e3ef4b5456ddirect
Gogolang.org/x/sys0.25.0direct
Gogithub.com/akavel/rsrc0.10.2indirect
Gogithub.com/dchest/jsmin0.0.0-20220218165748-59f39799265findirect
Gogithub.com/josephspurrier/goversioninfo1.4.1indirect
Gogithub.com/mattn/go-runewidth0.0.9indirect
Gogithub.com/nu7hatch/gouuid0.0.0-20131221200532-179d4d0c4d8dindirect
Gogithub.com/randall77/makefat0.0.0-20210315173500-7ddd0e42c844indirect
Gogolang.org/x/image0.20.0indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 16 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 1 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
golang.org/x/image0.20.0indirecthigh100.43.0
golang.org/x/sys0.25.0directunknown10.44.0

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics.