Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 09:42 UTC

npm / make-fetch-happen

making fetch happen for npm

JavaScriptCustom license★ 209 stars⑂ 39 forkssince Jun 2019View on GitHub ↗

npm/make-fetch-happen holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (84/100) and lowest on AI Readiness (43/100). It was last updated 19 days ago. 2 contributors account for most of its recent work.

90
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.

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

Ownership

npmOrganization
5,115 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
npmmake-fetch-happen16.0.1146,409,44411887 days agohttprequestfetchmean-girlscachingcachesubresource-integrity

Metrics by category

Vitality

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

68Good · 21% of overall
How it's scored
28.8/36Push recencylast push 19 days ago
5.5/36Commit cadence8/52 weeks with commits
13.3/18Commit volume29 commits in the last year
4/10OpenSSF Scorecard: Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year29
human_commit_share0.64
days_since_last_push19
active_weeks_last_year8
How it's scored
27/27Ships releases40 releases published
36/36Release recencylatest release 87 days ago
19.8/27Release cadencea release every ~64.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count40
latest_release_tagv15.0.6
releases_from_tagsno
days_since_latest_release87
mean_days_between_releases64.5
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?

78Good · 17% of overall
How it's scored
37.6/60Stars209 stars
13.2/25Forks39 forks
4.7/15Watchers8 watchers
Inputs used
forks39
stars209
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5Licenselicense 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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescoveralls.io, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads146,409,444 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmake-fetch-happen
dependents
ecosystemsnpm
total_downloads
monthly_downloads146,409,444
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?

82Excellent · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
12.9/22.5Commit distributiontop contributor authored 43% of commits
13.5/13.5Contributor breadth38 contributors
10/10OpenSSF Scorecard: Contributorsproject has 15 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled38
top_contributor_share0.427
How it's scored
34.2/42Issue resolution81% of issues closed
17.8/30PR acceptance191/322 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 7/9 approved changesets -- score normalized to 7
Inputs used
merged_prs191
open_issues8
closed_issues35
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.814
closed_unmerged_prs131
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach5,115 followers of npm
25/25Track record358 public repos, account ~12 yr old
Inputs used
followers5,115
owner_typeOrganization
is_verified
owner_loginnpm
public_repos358
account_age_days4,646
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 87 days ago
20/20Version history118 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmake-fetch-happen
ecosystemsnpm
any_deprecatedno
min_days_since_publish87

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests15 out of 15 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

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics1 topics
10/10Wiki
Inputs used
topicsnpm-cli
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
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-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-ReviewFound 7/9 approved changesets -- score normalized to 7
2.5/2.5Contributorsproject has 15 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
3/7.5Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
4.5/5SASTSAST tool detected but not run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.8
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 advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages40
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:make-fetch-happen@16.0.1 runtime dependency closure — what installing the published package pulls in — 40 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.

43Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history64 of 64 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
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance19 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_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.19
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
52.7/55Manageable file sizes1/24 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes67,209
source_files_sampled24
oversized_source_files1

Key facts

209GitHub stars
38contributors
29commits, last 12 months
19days since last push
40releases
2bus factor
8open 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 ★ / 39 ⇿
0Stars
39Forks
40Releases

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.

01325383722019-072023-012026-06
Major 7Minor 3Patch 30

Each point covers 7 days.

OpenSSF Scorecard 6.8 / 10
6.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-22 09:42 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-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 7/9 approved changesets -- score normalized to 7
10Contributorsproject has 15 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
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 12
RegistryPackageVersion constraintManifest
npm@gar/promise-retry^1.0.0package.json
npm@npmcli/agent^5.0.0package.json
npm@npmcli/redact^5.0.0package.json
npmcacache^21.0.0package.json
npmhttp-cache-semantics^4.1.1package.json
npmminipass^7.0.2package.json
npmminipass-fetch^6.0.0package.json
npmminipass-flush^1.0.5package.json
npmminipass-pipeline^1.2.4package.json
npmnegotiator^1.0.0package.json
npmproc-log^7.0.0package.json
npmssri^14.0.0package.json
All dependencies 18

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

RegistryPackageVersionRelation
npm@gar/promise-retry^1.0.0direct
npm@npmcli/agent^5.0.0direct
npm@npmcli/redact^5.0.0direct
npmcacache^21.0.0direct
npmhttp-cache-semantics^4.1.1direct
npmminipass^7.0.2direct
npmminipass-fetch^6.0.0direct
npmminipass-flush^1.0.5direct
npmminipass-pipeline^1.2.4direct
npmnegotiator^1.0.0direct
npmproc-log^7.0.0direct
npmssri^14.0.0direct
npm@npmcli/eslint-config^7.0.0indirect
npm@npmcli/template-oss5.1.1indirect
npmnock^13.2.4indirect
npmsafe-buffer^5.2.1indirect
npmstandard-version^9.3.2indirect
npmtap^16.0.0indirect
Dependency advisories 0

Installing npm:make-fetch-happen@16.0.1 pulls in 40 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 statisticsnpm.