Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 23:52 UTC

MoOx / caniuse-api

Request caniuse.com data to check browsers compatibilities

TypeScriptMIT★ 358 stars⑂ 25 forkssince Dec 2014View on GitHub ↗

MoOx/caniuse-api holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (77/100) and lowest on Vitality (43/100). It was last updated 39 days ago. 2 contributors account for most of its recent work.

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.

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

Ownership

Max T.Personal account

1,271 followers161 public repossince Nov 2009Freelance at MoOx.io

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
npm	caniuse-api	4.0.0	70,147,390	19	140 days ago	caniuse browserslist

Metrics by category

Vitality

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

43Weak · 21% of overall

Development activity

27At Risk

How it's scored

18/36	Push recency — last push 39 days ago
0.7/36	Commit cadence — 1/52 weeks with commits
8.6/18	Commit volume — 8 commits in the last year
0/10	OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Inputs used

commits_last_year	8
human_commit_share	1
days_since_last_push	39
active_weeks_last_year	1

Release discipline

66Good

How it's scored

27/27	Ships releases — 13 releases published
27/36	Release recency — latest release 140 days ago
5.4/27	Release cadence — a release every ~431.1 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	13
latest_release_tag	4.0.0
releases_from_tags	no
days_since_latest_release	140
mean_days_between_releases	431.1

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?

77Good · 17% of overall

Popularity & adoption

56Moderate

How it's scored

41.4/60	Stars — 358 stars
11.5/25	Forks — 25 forks
2.7/15	Watchers — 4 watchers

Inputs used

forks	25
stars	358
watchers	4
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

85Excellent

How it's scored

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

Inputs used

has_readme	yes
has_license	yes
readme_badges	9
has_contributing	yes
has_issue_template	no
has_code_of_conduct	yes
readme_badge_services	shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 70,147,390 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	caniuse-api
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	70,147,390
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?

70Good · 23% of overall

Maintainer resilience (bus factor)

61Moderate

How it's scored

25.2/54	Bus factor — 2 contributor(s) cover half of all commits
12/22.5	Commit distribution — top contributor authored 47% of commits
13.5/13.5	Contributor breadth — 12 contributors
10/10	OpenSSF Scorecard: Contributors — project has 11 contributing companies or organizations

Inputs used

bus_factor	2
contributors_sampled	12
top_contributor_share	0.467

Issue & PR responsiveness

53Moderate

How it's scored

30.5/42	Issue resolution — 73% of issues closed
12.9/30	PR acceptance — 18/42 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15	OpenSSF Scorecard: Code-Review — Found 6/26 approved changesets -- score normalized to 2

Inputs used

merged_prs	18
open_issues	17
closed_issues	45
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.726
closed_unmerged_prs	24
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

72Good

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
22.3/25	Owner reach — 1,271 followers of MoOx
25/25	Track record — 161 public repos, account ~16 yr old

Inputs used

followers	1,271
owner_type	User
is_verified	—
owner_login	MoOx
public_repos	161
account_age_days	6,174

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on npm
35/35	Publish recency — latest publish 140 days ago
20/20	Version history — 19 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	caniuse-api
ecosystems	npm
any_deprecated	no
min_days_since_publish	140

Engineering Quality

Are baseline engineering and documentation practices in place?

58Moderate · 19% of overall

Engineering practices

56Moderate

How it's scored

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

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	yes
has_linter_config	no
has_precommit_config	no

Documentation

60Moderate

How it's scored

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

Inputs used

topics	caniuse, caniuse-db
has_wiki	yes
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?

51Moderate · 16% of overall

Security posture

39Weak

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/2.5	CI-Tests — 1 out of 8 merged PRs checked by a CI test -- score normalized to 1
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5	Code-Review — Found 6/26 approved changesets -- score normalized to 2
2.5/2.5	Contributors — project has 11 contributing companies or organizations
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
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 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5	Packaging — no data
1.5/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
5/5	Security-Policy — security policy file detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
5.2/7.5	Vulnerabilities — 3 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	16
scorecard_version	v5.5.0
checks_inconclusive	2
scorecard_aggregate	3.9

Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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	8
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:caniuse-api@4.0.0 runtime dependency closure — what installing the published package pulls in — 8 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.

46Weak · 4% of overall

Agent context & guidance

17Critical

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.311
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

48Weak

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — tsconfig.json
10/10	Reproducible environment — lockfile
2.2/10	Demonstrated agent practice — 1 of the last 90 commits agent-authored or agent-credited
0/8	Automated maintenance — no automated dependency updates observed
3/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3

Inputs used

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

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — TypeScript (statically typed)
55/55	Manageable file sizes — 0/4 source files over 60KB

Inputs used

primary_language	TypeScript
largest_source_bytes	3,473
source_files_sampled	4
oversized_source_files	0

Key facts

358GitHub stars

12contributors

8commits, last 12 months

39days since last push

13releases

2bus factor

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

0Stars

25Forks

11Releases

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 2Minor 2Patch 7

Each point covers 10 days.

OpenSSF Scorecard 3.9 / 10

3.9aggregate

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-20 23:52 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
1	CI-Tests	1 out of 8 merged PRs checked by a CI test -- score normalized to 1
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
2	Code-Review	Found 6/26 approved changesets -- score normalized to 2
10	Contributors	project has 11 contributing companies or organizations
10	Dangerous-Workflow	no dangerous workflow patterns detected
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
0	Maintained	0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/a	Packaging	packaging workflow not detected
3	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 3
0	SAST	SAST tool is not run on all commits -- score normalized to 0
10	Security-Policy	security policy file detected
n/a	Signed-Releases	no releases found
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
7	Vulnerabilities	3 existing vulnerabilities detected

Direct dependencies 2

Registry	Package	Version constraint	Manifest
npm	browserslist	`^4.0.0`	package.json
npm	caniuse-lite	`^1.0.0`	package.json

All dependencies 184

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

Registry	Package	Version	Relation
npm	browserslist	`4.28.2`	direct
npm	caniuse-lite	`1.0.30001793`	direct
npm	@esbuild/aix-ppc64	`0.28.0`	indirect
npm	@esbuild/android-arm	`0.28.0`	indirect
npm	@esbuild/android-arm64	`0.28.0`	indirect
npm	@esbuild/android-x64	`0.28.0`	indirect
npm	@esbuild/darwin-arm64	`0.28.0`	indirect
npm	@esbuild/darwin-x64	`0.28.0`	indirect
npm	@esbuild/freebsd-arm64	`0.28.0`	indirect
npm	@esbuild/freebsd-x64	`0.28.0`	indirect
npm	@esbuild/linux-arm	`0.28.0`	indirect
npm	@esbuild/linux-arm64	`0.28.0`	indirect
npm	@esbuild/linux-ia32	`0.28.0`	indirect
npm	@esbuild/linux-loong64	`0.28.0`	indirect
npm	@esbuild/linux-mips64el	`0.28.0`	indirect
npm	@esbuild/linux-ppc64	`0.28.0`	indirect
npm	@esbuild/linux-riscv64	`0.28.0`	indirect
npm	@esbuild/linux-s390x	`0.28.0`	indirect
npm	@esbuild/linux-x64	`0.28.0`	indirect
npm	@esbuild/netbsd-arm64	`0.28.0`	indirect
npm	@esbuild/netbsd-x64	`0.28.0`	indirect
npm	@esbuild/openbsd-arm64	`0.28.0`	indirect
npm	@esbuild/openbsd-x64	`0.28.0`	indirect
npm	@esbuild/openharmony-arm64	`0.28.0`	indirect
npm	@esbuild/sunos-x64	`0.28.0`	indirect
npm	@esbuild/win32-arm64	`0.28.0`	indirect
npm	@esbuild/win32-ia32	`0.28.0`	indirect
npm	@esbuild/win32-x64	`0.28.0`	indirect
npm	@ljharb/resumer	`0.0.1`	indirect
npm	@ljharb/through	`2.3.14`	indirect
npm	@oxlint/binding-android-arm-eabi	`1.68.0`	indirect
npm	@oxlint/binding-android-arm64	`1.68.0`	indirect
npm	@oxlint/binding-darwin-arm64	`1.68.0`	indirect
npm	@oxlint/binding-darwin-x64	`1.68.0`	indirect
npm	@oxlint/binding-freebsd-x64	`1.68.0`	indirect
npm	@oxlint/binding-linux-arm-gnueabihf	`1.68.0`	indirect
npm	@oxlint/binding-linux-arm-musleabihf	`1.68.0`	indirect
npm	@oxlint/binding-linux-arm64-gnu	`1.68.0`	indirect
npm	@oxlint/binding-linux-arm64-musl	`1.68.0`	indirect
npm	@oxlint/binding-linux-ppc64-gnu	`1.68.0`	indirect
npm	@oxlint/binding-linux-riscv64-gnu	`1.68.0`	indirect
npm	@oxlint/binding-linux-riscv64-musl	`1.68.0`	indirect
npm	@oxlint/binding-linux-s390x-gnu	`1.68.0`	indirect
npm	@oxlint/binding-linux-x64-gnu	`1.68.0`	indirect
npm	@oxlint/binding-linux-x64-musl	`1.68.0`	indirect
npm	@oxlint/binding-openharmony-arm64	`1.68.0`	indirect
npm	@oxlint/binding-win32-arm64-msvc	`1.68.0`	indirect
npm	@oxlint/binding-win32-ia32-msvc	`1.68.0`	indirect
npm	@oxlint/binding-win32-x64-msvc	`1.68.0`	indirect
npm	ansi-regex	`6.2.2`	indirect
npm	array-buffer-byte-length	`1.0.2`	indirect
npm	arraybuffer.prototype.slice	`1.0.4`	indirect
npm	async-function	`1.0.0`	indirect
npm	available-typed-arrays	`1.0.7`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	baseline-browser-mapping	`2.10.33`	indirect
npm	brace-expansion	`1.1.15`	indirect
npm	call-bind	`1.0.9`	indirect
npm	call-bind-apply-helpers	`1.0.2`	indirect
npm	call-bound	`1.0.4`	indirect
npm	chalk	`5.6.2`	indirect
npm	concat-map	`0.0.1`	indirect
npm	data-view-buffer	`1.0.2`	indirect
npm	data-view-byte-length	`1.0.2`	indirect
npm	data-view-byte-offset	`1.0.1`	indirect
npm	debug	`4.4.3`	indirect
npm	deep-equal	`1.1.2`	indirect
npm	define-data-property	`1.1.4`	indirect
npm	define-properties	`1.2.1`	indirect
npm	defined	`1.0.1`	indirect
npm	diff	`5.2.2`	indirect
npm	dotignore	`0.1.2`	indirect
npm	dunder-proto	`1.0.1`	indirect
npm	electron-to-chromium	`1.5.365`	indirect
npm	es-abstract	`1.24.2`	indirect
npm	es-define-property	`1.0.1`	indirect
npm	es-errors	`1.3.0`	indirect
npm	es-object-atoms	`1.1.2`	indirect
npm	es-set-tostringtag	`2.1.0`	indirect
npm	es-to-primitive	`1.3.0`	indirect
npm	esbuild	`0.28.0`	indirect
npm	esbuild-register	`3.6.0`	indirect
npm	escalade	`3.2.0`	indirect
npm	for-each	`0.3.5`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	function-bind	`1.1.2`	indirect
npm	function.prototype.name	`1.1.8`	indirect
npm	functions-have-names	`1.2.3`	indirect
npm	generator-function	`2.0.1`	indirect
npm	get-intrinsic	`1.3.0`	indirect
npm	get-proto	`1.0.1`	indirect
npm	get-symbol-description	`1.1.0`	indirect
npm	glob	`7.2.3`	indirect
npm	globalthis	`1.0.4`	indirect
npm	gopd	`1.2.0`	indirect
npm	has	`1.0.4`	indirect
npm	has-bigints	`1.1.0`	indirect
npm	has-property-descriptors	`1.0.2`	indirect
npm	has-proto	`1.2.0`	indirect
npm	has-symbols	`1.1.0`	indirect
npm	has-tostringtag	`1.0.2`	indirect
npm	hasown	`2.0.4`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	indirect
npm	internal-slot	`1.1.0`	indirect
npm	is-arguments	`1.2.0`	indirect
npm	is-array-buffer	`3.0.5`	indirect
npm	is-async-function	`2.1.1`	indirect
npm	is-bigint	`1.1.0`	indirect
npm	is-boolean-object	`1.2.2`	indirect
npm	is-callable	`1.2.7`	indirect
npm	is-core-module	`2.16.2`	indirect
npm	is-data-view	`1.0.2`	indirect
npm	is-date-object	`1.1.0`	indirect
npm	is-finalizationregistry	`1.1.1`	indirect
npm	is-generator-function	`1.1.2`	indirect
npm	is-map	`2.0.3`	indirect
npm	is-negative-zero	`2.0.3`	indirect
npm	is-number-object	`1.1.1`	indirect
npm	is-regex	`1.1.4`	indirect
npm	is-regex	`1.2.1`	indirect
npm	is-set	`2.0.3`	indirect
npm	is-shared-array-buffer	`1.0.4`	indirect
npm	is-string	`1.1.1`	indirect
npm	is-symbol	`1.1.1`	indirect
npm	is-typed-array	`1.1.15`	indirect
npm	is-weakmap	`2.0.2`	indirect
npm	is-weakref	`1.1.1`	indirect
npm	is-weakset	`2.0.4`	indirect
npm	isarray	`2.0.5`	indirect
npm	json5	`2.2.3`	indirect
npm	lodash.memoize	`4.1.2`	indirect
npm	lodash.uniq	`4.5.0`	indirect
npm	math-intrinsics	`1.1.0`	indirect
npm	minimatch	`3.1.5`	indirect
npm	minimist	`1.2.8`	indirect
npm	mock-property	`1.0.3`	indirect
npm	ms	`2.1.3`	indirect
npm	node-releases	`2.0.47`	indirect
npm	object-inspect	`1.12.3`	indirect
npm	object-inspect	`1.13.4`	indirect
npm	object-is	`1.1.6`	indirect
npm	object-keys	`1.1.1`	indirect
npm	object.assign	`4.1.7`	indirect
npm	once	`1.4.0`	indirect
npm	own-keys	`1.0.1`	indirect
npm	oxlint	`1.68.0`	indirect
npm	path-is-absolute	`1.0.1`	indirect
npm	path-parse	`1.0.7`	indirect
npm	picocolors	`1.1.1`	indirect
npm	possible-typed-array-names	`1.1.0`	indirect
npm	reflect.getprototypeof	`1.0.10`	indirect
npm	regexp.prototype.flags	`1.5.4`	indirect
npm	resolve	`1.22.12`	indirect
npm	safe-array-concat	`1.1.4`	indirect
npm	safe-push-apply	`1.0.0`	indirect
npm	safe-regex-test	`1.1.0`	indirect
npm	set-function-length	`1.2.2`	indirect
npm	set-function-name	`2.0.2`	indirect
npm	set-proto	`1.0.0`	indirect
npm	side-channel	`1.1.0`	indirect
npm	side-channel-list	`1.0.1`	indirect
npm	side-channel-map	`1.0.1`	indirect
npm	side-channel-weakmap	`1.0.2`	indirect
npm	stop-iteration-iterator	`1.1.0`	indirect
npm	string.prototype.trim	`1.2.10`	indirect
npm	string.prototype.trimend	`1.0.9`	indirect
npm	string.prototype.trimstart	`1.0.8`	indirect
npm	strip-ansi	`7.2.0`	indirect
npm	supports-preserve-symlinks-flag	`1.0.0`	indirect
npm	tap-arc	`1.3.2`	indirect
npm	tap-reader	`0.2.1`	indirect
npm	tape	`4.17.0`	indirect
npm	typed-array-buffer	`1.0.3`	indirect
npm	typed-array-byte-length	`1.0.3`	indirect
npm	typed-array-byte-offset	`1.0.4`	indirect
npm	typed-array-length	`1.0.8`	indirect
npm	unbox-primitive	`1.1.0`	indirect
npm	update-browserslist-db	`1.2.3`	indirect
npm	which-boxed-primitive	`1.1.1`	indirect
npm	which-builtin-type	`1.2.1`	indirect
npm	which-collection	`1.0.2`	indirect
npm	which-typed-array	`1.1.21`	indirect
npm	wrappy	`1.0.2`	indirect

Dependency advisories 0

Installing npm:caniuse-api@4.0.0 pulls in 8 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