Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 21:30 UTC

npm / template-oss

a template package for npm CLI team development

JavaScriptCustom license★ 38 stars⑂ 26 forkssince Aug 2021View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

npm/template-oss holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (80/100) and lowest on AI Readiness (44/100). It was last updated 7 days ago. A single contributor accounts for most of its recent work.

86
overall / 100
Excellent

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.

86
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 72 is calibrated to 86 on the published index scale (record calibration 2026-08-02).

Ownership

npmOrganization · verified domain
5,264 followers358 public repossince Dec 2013

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@npmcli/template-oss5.1.133,974116125 days agonpmoss

Metrics by category

Vitality

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

71Good · 21% of overall
How it's scored
36/36Push recency — last push 7 days ago
6.9/36Commit cadence — 10/52 weeks with commits
14.7/18Commit volume — 42 commits in the last year
0/10OpenSSF Scorecard: Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year42
human_commit_share0.63
days_since_last_push7
active_weeks_last_year10
How it's scored
27/27Ships releases — 100 releases published
27/36Release recency — latest release 125 days ago
27/27Release cadence — a release every ~26.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv5.1.1
releases_from_tagsno
days_since_latest_release125
mean_days_between_releases26.6
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

66Good · 17% of overall
How it's scored
25.4/60Stars — 38 stars
11.7/25Forks — 26 forks
5.8/15Watchers — 12 watchers
Inputs used
forks26
stars38
watchers12
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateyes
How it's scored
60.4/80Monthly downloads — 33,974 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@npmcli/template-oss
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads33,974
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

80Excellent · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.4/22.5Commit distribution — top contributor authored 63% of commits
12.2/13.5Contributor breadth — 9 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.626
How it's scored
38.8/42Issue resolution — 92% of issues closed
24.1/30PR acceptance — 388/483 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs388
open_issues6
closed_issues72
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.923
closed_unmerged_prs95
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 5,264 followers of npm
25/25Track record — 358 public repos, account ~12 yr old
Inputs used
followers5,264
owner_typeOrganization
is_verifiedyes
owner_loginnpm
public_repos358
account_age_days4,705

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 125 days ago
20/20Version history — 116 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@npmcli/template-oss
ecosystemsnpm
any_deprecatedno
min_days_since_publish125

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows — 9 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 21 out of 21 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 1 topics
10/10Wiki
Inputs used
topicsnpm-cli
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?

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 21 out of 21 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 6 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
0/7.5Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
4.5/5SAST — SAST tool detected but not run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.7
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages353
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:@npmcli/template-oss@5.1.1 runtime dependency closure — what installing the published package pulls in — 353 packages. 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.

44Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 63 of 63 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.js
0/11Static type checking
0/10Reproducible environment
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 14 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0.14
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
54.4/55Manageable file sizes — 1/99 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes145,395
source_files_sampled99
oversized_source_files1

Key facts

38GitHub stars
9contributors
42commits, last 12 months
7days since last push
100releases
1bus factor
6open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 26 ⇿
0Stars
26Forks
93Releases

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.

048121620242412022-032024-052026-08
Major 3Minor 39Patch 51

Each point covers 5 days.

OpenSSF Scorecard 6.7 / 10
6.7aggregate

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-10-19 21:30 UTC

10Binary-Artifactsno binaries found in the repo
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
10CI-Tests21 out of 21 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 6 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 26
RegistryPackageVersion constraintManifest
npm@actions/core^2.0.0package.json
npm@commitlint/cli^20.1.0package.json
npm@commitlint/config-conventional^20.0.0package.json
npm@isaacs/string-locale-compare^1.1.0package.json
npm@npmcli/arborist^10.0.0-pre.0.0package.json
npm@npmcli/git^8.0.0package.json
npm@npmcli/map-workspaces^6.0.0package.json
npm@npmcli/package-json^8.0.0package.json
npm@octokit/rest^22.0.0package.json
npmdedent^1.5.1package.json
npmdiff^8.0.2package.json
npmglob^13.0.0package.json
npmhandlebars^4.7.7package.json
npmhosted-git-info^10.1.1package.json
npmini^7.0.0package.json
npmjson-parse-even-better-errors^6.0.0package.json
npmjust-deep-map-values^1.1.1package.json
npmjust-diff^6.0.0package.json
npmjust-omit^2.2.0package.json
npmlodash^4.17.21package.json
npmminimatch^10.0.3package.json
npmnpm-package-arg^14.0.0package.json
npmproc-log^7.0.0package.json
npmrelease-please^17.1.1package.json
npmsemver^7.3.5package.json
npmyaml^2.1.1package.json
All dependencies 34

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

RegistryPackageVersionRelation
npm@actions/core^2.0.0direct
npm@commitlint/cli^20.1.0direct
npm@commitlint/config-conventional^20.0.0direct
npm@isaacs/string-locale-compare^1.1.0direct
npm@npmcli/arborist^10.0.0-pre.0.0direct
npm@npmcli/git^8.0.0direct
npm@npmcli/map-workspaces^6.0.0direct
npm@npmcli/package-json^8.0.0direct
npm@octokit/rest^22.0.0direct
npmdedent^1.5.1direct
npmdiff^8.0.2direct
npmglob^13.0.0direct
npmhandlebars^4.7.7direct
npmhosted-git-info^10.1.1direct
npmini^7.0.0direct
npmjson-parse-even-better-errors^6.0.0direct
npmjust-deep-map-values^1.1.1direct
npmjust-diff^6.0.0direct
npmjust-omit^2.2.0direct
npmlodash^4.17.21direct
npmminimatch^10.0.3direct
npmnpm-package-arg^14.0.0direct
npmproc-log^7.0.0direct
npmrelease-please^17.1.1direct
npmsemver^7.3.5direct
npmyaml^2.1.1direct
npm@github/prettier-config0.0.6indirect
npm@npmcli/eslint-config^6.0.1indirect
npm@npmcli/eslint-config^7.0.0indirect
npmeslint-config-prettier^10.1.8indirect
npmnock^14.0.6indirect
npmprettier^3.2.5indirect
npmtap^16.0.0indirect
npmtap^21.0.1indirect
Dependency advisories 0

Installing npm:@npmcli/template-oss@5.1.1 pulls in 353 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.34.0 — full methodology · metrics wiki.

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