Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-24 04:27 UTC

npm / fstream

Advanced FS Streaming for Node

JavaScriptISC★ 207 stars⑂ 53 forkssince Oct 2011archivedView on GitHub ↗

npm/fstream holds a health index of 12 out of 100, placing it in the Critical band. It scores highest on Community & Adoption (66/100) and lowest on Vitality (13/100). The repository is archived, so no further maintenance is expected.

overall / 100

Critical

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.

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)

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

Ownership

npmOrganization · verified domain

5,184 followers358 public repossince Dec 2013

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish
npm	fstream⚠ This package is no longer supported.	1.0.12	60,978,464	46	2689 days ago

Metrics by category

Vitality

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

13Critical · 21% of overall

Development activity

1Critical

Abandonment alert

Work has arrived and nobody has attended to it

archived on GitHub by its maintainersOverall rating: Critical ceiling

Silence alone is never the finding — a small, finished library may need no commits for years. This alert requires both: no human commit for a long time, and obligations the project is visibly not discharging. Automated commits do not count as maintenance.

How abandonment is assessed

How it's scored

0/36	Push recency — last push 1,925 days ago
0/36	Commit cadence — 0/52 weeks with commits
0/18	Commit volume — 0 commits in the last year
0/10	OpenSSF Scorecard: Maintained — project is archived

Inputs used

commits_last_year	0
human_commit_share	1
days_since_last_push	1,925
active_weeks_last_year	0

Release discipline

32At Risk

How it's scored

16.2/27	Ships releases — 46 version tags (no GitHub releases)
0/36	Release recency — latest release 2,689 days ago
12.6/27	Release cadence — a release every ~181 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	46
latest_release_tag	v1.0.12
releases_from_tags	yes
days_since_latest_release	2,689
mean_days_between_releases	181

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

Popularity & adoption

52Moderate

How it's scored

37.5/60	Stars — 207 stars
14.3/25	Forks — 53 forks
0/15	Watchers — 0 watchers

Inputs used

forks	53
stars	207
watchers	0
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

57Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (ISC)
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
6.3/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	0
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	yes

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 60,978,464 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	fstream
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	60,978,464
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?

52Moderate · 23% of overall

Maintainer resilience (bus factor)

37Weak

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
4.2/22.5	Commit distribution — top contributor authored 81% of commits
13.5/13.5	Contributor breadth — 19 contributors
10/10	OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations

Inputs used

bus_factor	1
contributors_sampled	19
top_contributor_share	0.812

Issue & PR responsiveness

24At Risk

How it's scored

15.8/42	Issue resolution — 38% of issues closed
5.5/30	PR acceptance — 4/22 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 2/30 approved changesets -- score normalized to 0

Inputs used

merged_prs	4
open_issues	25
closed_issues	15
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.375
closed_unmerged_prs	18
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

100Exceptional

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
25/25	Owner reach — 5,184 followers of npm
25/25	Track record — 358 public repos, account ~12 yr old

Inputs used

followers	5,184
owner_type	Organization
is_verified	yes
owner_login	npm
public_repos	358
account_age_days	4,679

Package maintenance

49Weak

How it's scored

25/25	Published & resolvable — 1 package(s) on npm
4/35	Publish recency — latest publish 2,689 days ago
20/20	Version history — 46 published versions
0/20	Not deprecated — fstream: This package is no longer supported.

Inputs used

packages	fstream
ecosystems	npm
any_deprecated	yes
min_days_since_publish	2,689

Engineering Quality

Are baseline engineering and documentation practices in place?

17Critical · 19% of overall

Engineering practices

1Critical

How it's scored

0/24	CI workflows
0/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0

Inputs used

has_ci	no
has_tests	no
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

40Weak

How it's scored

30/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
0/10	Topics
0/10	Wiki

Inputs used

topics	—
has_wiki	no
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	no
has_description	yes

Security

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

34At Risk · 16% of overall

Security posture

18Critical

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
0/2.5	CI-Tests — 0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 2/30 approved changesets -- score normalized to 0
2.5/2.5	Contributors — project has 8 contributing companies or organizations
0/10	Dangerous-Workflow — no data
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
0/7.5	Maintained — project is archived
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — no data
0/7.5	Vulnerabilities — 70 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	13
scorecard_version	v5.5.0
checks_inconclusive	5
scorecard_aggregate	1.8

Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25	Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	0
affected_packages	0
assessed_packages	15
unassessed_packages	0
affected_by_severity	none
direct_affected_packages	0

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:fstream@1.0.12 runtime dependency closure — what installing the published package pulls in — 15 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.

31At Risk · 4% of overall

Agent context & guidance

11Critical

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
10.7/40	Legible commit history — 20 of 100 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.2
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

11Critical

How it's scored

0/18	One-command bootstrap
0/22	Automated tests
0/11	Lint / format config
0/11	Static type checking
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	no
lockfiles	package-lock.json
has_dockerfile	no
typed_language	no
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

55Moderate

How it's scored

0/45	Type-checkable code — JavaScript without a type-check config
55/55	Manageable file sizes — 0/19 source files over 60KB

Inputs used

primary_language	JavaScript
largest_source_bytes	11,044
source_files_sampled	19
oversized_source_files	0

Machine-readable interfaces

100Exceptional

How it's scored

0/40	API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20	MCP server — not applicable to this kind of software
40/40	Runnable examples — examples

Inputs used

example_dirs	examples
has_mcp_signal	no
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

207GitHub stars

19contributors

0commits, last 12 months

1,925days since last push

46releases

1bus factor

25open 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 ★ / 53 ⇿

0Stars

53Forks

32Releases

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.

Major 1Minor 0Patch 31

Each point covers 13 days.

OpenSSF Scorecard 1.8 / 10

1.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-09-24 04:26 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
0	CI-Tests	0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 2/30 approved changesets -- score normalized to 0
10	Contributors	project has 8 contributing companies or organizations
n/a	Dangerous-Workflow	no workflows found
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
0	Maintained	project is archived
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
n/a	Token-Permissions	No tokens found
0	Vulnerabilities	70 existing vulnerabilities detected

Direct dependencies 4

Registry	Package	Version constraint	Manifest
npm	graceful-fs	`^4.1.2`	package.json
npm	inherits	`~2.0.0`	package.json
npm	mkdirp	`^0.5 0`	package.json
npm	rimraf	`2`	package.json

All dependencies 199

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

Registry	Package	Version	Relation
npm	graceful-fs	`1.1.14`	direct
npm	graceful-fs	`4.1.15`	direct
npm	inherits	`2.0.0`	direct
npm	inherits	`2.0.1`	direct
npm	mkdirp	`0.5.0`	direct
npm	rimraf	`2.0.2`	direct
npm	rimraf	`2.3.4`	direct
npm	abbrev	`1.0.7`	indirect
npm	align-text	`0.1.1`	indirect
npm	amdefine	`0.1.0`	indirect
npm	ansi-regex	`1.1.1`	indirect
npm	ansi-styles	`2.0.1`	indirect
npm	argparse	`0.1.16`	indirect
npm	argparse	`1.0.2`	indirect
npm	asap	`1.0.0`	indirect
npm	asn1	`0.1.11`	indirect
npm	assert-plus	`0.1.5`	indirect
npm	async	`0.2.10`	indirect
npm	async	`0.9.2`	indirect
npm	aws-sign2	`0.5.0`	indirect
npm	balanced-match	`0.2.0`	indirect
npm	boom	`0.4.2`	indirect
npm	brace-expansion	`1.1.0`	indirect
npm	buffer-equal	`0.0.1`	indirect
npm	camelcase	`1.1.0`	indirect
npm	center-align	`0.1.1`	indirect
npm	chalk	`1.0.0`	indirect
npm	cli-width	`1.0.1`	indirect
npm	cliui	`2.1.0`	indirect
npm	combined-stream	`0.0.7`	indirect
npm	concat-map	`0.0.1`	indirect
npm	concat-stream	`1.4.8`	indirect
npm	core-util-is	`1.0.1`	indirect
npm	coveralls	`2.11.2`	indirect
npm	cryptiles	`0.2.2`	indirect
npm	ctype	`0.5.3`	indirect
npm	d	`0.1.1`	indirect
npm	debug	`0.7.4`	indirect
npm	debug	`2.2.0`	indirect
npm	decamelize	`1.0.0`	indirect
npm	deep-equal	`1.0.0`	indirect
npm	deep-is	`0.1.3`	indirect
npm	delayed-stream	`0.0.5`	indirect
npm	dezalgo	`1.0.2`	indirect
npm	diff	`1.4.0`	indirect
npm	doctrine	`0.6.4`	indirect
npm	es5-ext	`0.10.7`	indirect
npm	es6-iterator	`0.1.3`	indirect
npm	es6-map	`0.1.1`	indirect
npm	es6-set	`0.1.1`	indirect
npm	es6-symbol	`0.1.1`	indirect
npm	es6-symbol	`2.0.1`	indirect
npm	es6-weak-map	`0.1.4`	indirect
npm	escape-string-regexp	`1.0.3`	indirect
npm	escodegen	`1.6.1`	indirect
npm	escope	`3.1.0`	indirect
npm	esformatter	`0.6.1`	indirect
npm	esformatter-eol-last	`1.0.0`	indirect
npm	esformatter-literal-notation	`1.0.0`	indirect
npm	esformatter-quotes	`1.0.1`	indirect
npm	esformatter-spaced-lined-comment	`2.0.1`	indirect
npm	eslint	`0.21.2`	indirect
npm	eslint-config-standard	`2.0.0`	indirect
npm	eslint-plugin-react	`2.4.0`	indirect
npm	espree	`2.0.2`	indirect
npm	esprima	`1.0.4`	indirect
npm	esprima	`1.2.5`	indirect
npm	esprima	`2.1.0`	indirect
npm	esprima	`2.2.0`	indirect
npm	esrecurse	`3.1.1`	indirect
npm	estraverse	`1.9.3`	indirect
npm	estraverse	`2.0.0`	indirect
npm	estraverse	`3.1.0`	indirect
npm	estraverse-fb	`1.3.1`	indirect
npm	esutils	`1.1.6`	indirect
npm	event-emitter	`0.3.3`	indirect
npm	events-to-array	`1.0.2`	indirect
npm	fast-levenshtein	`1.0.6`	indirect
npm	figures	`1.3.5`	indirect
npm	fileset	`0.1.5`	indirect
npm	find-root	`0.1.1`	indirect
npm	first-chunk-stream	`1.0.0`	indirect
npm	foreground-child	`1.2.0`	indirect
npm	forever-agent	`0.5.2`	indirect
npm	form-data	`0.1.4`	indirect
npm	get-stdin	`4.0.1`	indirect
npm	glob	`3.2.11`	indirect
npm	glob	`4.5.3`	indirect
npm	glob	`5.0.10`	indirect
npm	globals	`6.4.1`	indirect
npm	handlebars	`3.0.0`	indirect
npm	has-ansi	`1.0.3`	indirect
npm	hawk	`1.1.1`	indirect
npm	hoek	`0.9.1`	indirect
npm	http-signature	`0.10.1`	indirect
npm	ignore	`2.2.15`	indirect
npm	inflight	`1.0.4`	indirect
npm	inquirer	`0.8.5`	indirect
npm	is-absolute	`0.1.7`	indirect
npm	is-relative	`0.1.3`	indirect
npm	is-utf8	`0.2.0`	indirect
npm	isarray	`0.0.1`	indirect
npm	istanbul	`0.3.14`	indirect
npm	js-yaml	`3.0.1`	indirect
npm	js-yaml	`3.3.1`	indirect
npm	json-stringify-safe	`5.0.1`	indirect
npm	kind-of	`1.1.0`	indirect
npm	lcov-parse	`0.0.6`	indirect
npm	levn	`0.2.5`	indirect
npm	lodash	`3.9.3`	indirect
npm	log-driver	`1.2.4`	indirect
npm	longest	`1.0.1`	indirect
npm	lru-cache	`2.6.4`	indirect
npm	mime	`1.2.11`	indirect
npm	mime-types	`1.0.2`	indirect
npm	minimatch	`0.3.0`	indirect
npm	minimatch	`0.4.0`	indirect
npm	minimatch	`2.0.8`	indirect
npm	minimist	`0.0.10`	indirect
npm	minimist	`0.0.8`	indirect
npm	minimist	`1.1.1`	indirect
npm	mout	`0.11.0`	indirect
npm	ms	`0.7.1`	indirect
npm	mute-stream	`0.0.4`	indirect
npm	node-uuid	`1.4.3`	indirect
npm	nopt	`3.0.2`	indirect
npm	npm-path	`1.0.1`	indirect
npm	npm-run	`1.1.1`	indirect
npm	nyc	`2.2.1`	indirect
npm	oauth-sign	`0.3.0`	indirect
npm	object-assign	`2.0.0`	indirect
npm	once	`1.3.2`	indirect
npm	opener	`1.4.1`	indirect
npm	optimist	`0.3.7`	indirect
npm	optimist	`0.6.1`	indirect
npm	optionator	`0.5.0`	indirect
npm	path-is-absolute	`1.0.0`	indirect
npm	prelude-ls	`1.1.2`	indirect
npm	protochain	`1.0.2`	indirect
npm	qs	`1.0.2`	indirect
npm	readable-stream	`1.1.13`	indirect
npm	readline2	`0.1.1`	indirect
npm	repeat-string	`1.5.2`	indirect
npm	request	`2.40.0`	indirect
npm	resolve	`1.1.6`	indirect
npm	right-align	`0.1.1`	indirect
npm	rocambole	`0.3.6`	indirect
npm	rocambole	`0.6.0`	indirect
npm	rocambole-indent	`2.0.4`	indirect
npm	rocambole-linebreak	`1.0.1`	indirect
npm	rocambole-node	`1.0.0`	indirect
npm	rocambole-token	`1.2.1`	indirect
npm	rocambole-whitespace	`1.0.0`	indirect
npm	run-parallel	`1.1.1`	indirect
npm	rx	`2.5.2`	indirect
npm	semver	`2.2.1`	indirect
npm	semver	`4.3.6`	indirect
npm	serializerr	`1.0.1`	indirect
npm	sigmund	`1.0.1`	indirect
npm	signal-exit	`2.1.2`	indirect
npm	sntp	`0.2.4`	indirect
npm	source-map	`0.1.43`	indirect
npm	spawn-wrap	`1.0.1`	indirect
npm	sprintf-js	`1.0.2`	indirect
npm	standard	`4.0.0`	indirect
npm	standard-format	`1.3.6`	indirect
npm	stdin	`0.0.1`	indirect
npm	string.prototype.endswith	`0.2.0`	indirect
npm	string_decoder	`0.10.31`	indirect
npm	stringstream	`0.0.4`	indirect
npm	strip-ansi	`2.0.1`	indirect
npm	strip-bom	`1.0.0`	indirect
npm	strip-json-comments	`0.1.3`	indirect
npm	strip-json-comments	`1.0.2`	indirect
npm	supports-color	`1.3.1`	indirect
npm	sync-exec	`0.5.0`	indirect
npm	tap	`1.2.0`	indirect
npm	tap-mocha-reporter	`0.0.13`	indirect
npm	tap-parser	`1.1.5`	indirect
npm	text-table	`0.2.0`	indirect
npm	through	`2.3.7`	indirect
npm	tough-cookie	`1.2.0`	indirect
npm	tunnel-agent	`0.4.0`	indirect
npm	type-check	`0.3.1`	indirect
npm	typedarray	`0.0.6`	indirect
npm	uglify-js	`2.3.6`	indirect
npm	underscore	`1.7.0`	indirect
npm	underscore.string	`2.4.0`	indirect
npm	uniq	`1.0.1`	indirect
npm	user-home	`1.1.1`	indirect
npm	which	`1.0.9`	indirect
npm	which	`1.1.1`	indirect
npm	window-size	`0.1.0`	indirect
npm	wordwrap	`0.0.2`	indirect
npm	wordwrap	`0.0.3`	indirect
npm	wrappy	`1.0.1`	indirect
npm	xml-escape	`1.0.0`	indirect
npm	xtend	`4.0.0`	indirect
npm	yargs	`3.10.0`	indirect

Dependency advisories 0

Installing npm:fstream@1.0.12 pulls in 15 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.

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.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records