Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 08:32 UTC

bahmutov / start-server-and-test

Starts server, waits for URL, then runs test command; when the tests end, shuts down server

JavaScriptMIT★ 1,581 stars⑂ 97 forkssince Nov 2017View on GitHub ↗

KindCommand-line toolLibraryhow this is determined

bahmutov/start-server-and-test holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Vitality (88/100) and lowest on AI Readiness (47/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

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.

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

Ownership

Gleb BahmutovPersonal account

4,949 followers1,280 public repossince Aug 2012

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	start-server-and-test	3.0.12	7,706,454	100	44 days ago	ci parallel server start test utility wait

Metrics by category

Vitality

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

88Excellent · 21% of overall

Development activity

80Excellent

How it's scored

36/36	Push recency — last push 1 days ago
15.9/36	Commit cadence — 23/52 weeks with commits
18/18	Commit volume — 106 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	106
human_commit_share	0.66
days_since_last_push	1
active_weeks_last_year	23

Release discipline

100Exceptional

How it's scored

27/27	Ships releases — 100 releases published
36/36	Release recency — latest release 44 days ago
27/27	Release cadence — a release every ~9.2 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	100
latest_release_tag	v3.0.12
releases_from_tags	no
days_since_latest_release	44
mean_days_between_releases	9.2

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?

75Good · 17% of overall

Popularity & adoption

74Good

How it's scored

51.9/60	Stars — 1,581 stars
16.5/25	Forks — 97 forks
5.6/15	Watchers — 11 watchers

Inputs used

forks	97
stars	1,581
watchers	11
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

58Moderate

How it's scored

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

Inputs used

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

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 7,706,454 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	start-server-and-test
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	7,706,454
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?

72Good · 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.5/22.5	Commit distribution — top contributor authored 45% of commits
13.5/13.5	Contributor breadth — 27 contributors
10/10	OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations

Inputs used

bus_factor	2
contributors_sampled	27
top_contributor_share	0.446

Issue & PR responsiveness

60Moderate

How it's scored

28.5/42	Issue resolution — 68% of issues closed
24.1/30	PR acceptance — 306/381 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 0/9 approved changesets -- score normalized to 0

Inputs used

merged_prs	306
open_issues	48
closed_issues	101
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	2
prs_decided_30d	2
issue_closed_ratio	0.678
closed_unmerged_prs	75
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

75Good

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
25/25	Owner reach — 4,949 followers of bahmutov
25/25	Track record — 1,280 public repos, account ~14 yr old

Inputs used

followers	4,949
owner_type	User
is_verified	—
owner_login	bahmutov
public_repos	1,280
account_age_days	5,134

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 44 days ago
20/20	Version history — 100 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	start-server-and-test
ecosystems	npm
any_deprecated	no
min_days_since_publish	44

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall

Engineering practices

68Good

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
0/6.4	.editorconfig
20/20	OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
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 — 5 topics
10/10	Wiki

Inputs used

topics	cli, utility, test, server, startup
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?

68Good · 16% of overall

Security posture

60Moderate

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
2.5/2.5	CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/9 approved changesets -- score normalized to 0
2.5/2.5	Contributors — project has 12 contributing companies or organizations
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5	Dependency-Update-Tool — update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
7.5/7.5	Maintained — 30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
0/5	Packaging — no data
5/5	Pinned-Dependencies — all dependencies are pinned
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 — detected GitHub workflow tokens with excessive permissions
6/7.5	Vulnerabilities — 2 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	15
scorecard_version	v5.5.0
checks_inconclusive	3
scorecard_aggregate	6

Excluded from scoring (no data or not applicable): Branch-Protection, 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	63
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:start-server-and-test@3.0.12 runtime dependency closure — what installing the published package pulls in — 63 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.

47Weak · 4% of overall

Agent context & guidance

40Weak

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	1
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

50Moderate

How it's scored

0/18	One-command bootstrap
22/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
8/8	Automated maintenance — 34 of the last 100 commits are automated dependency updates
10/10	OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned

Inputs used

has_nix	no
has_tests	yes
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.34

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/17 source files over 60KB

Inputs used

primary_language	JavaScript
largest_source_bytes	12,273
source_files_sampled	17
oversized_source_files	0

Key facts

1,581GitHub stars

27contributors

106commits, last 12 months

1days since last push

100releases

2bus factor

48open 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 ★ / 97 ⇿

0Stars

97Forks

99Releases

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 15Patch 82

Each point covers 8 days.

OpenSSF Scorecard 6.0 / 10

6.0aggregate

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-15 08:31 UTC

10	Binary-Artifacts	no binaries found in the repo
n/a	Branch-Protection	internal 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
10	CI-Tests	30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 0/9 approved changesets -- score normalized to 0
10	Contributors	project has 12 contributing companies or organizations
10	Dangerous-Workflow	no dangerous workflow patterns detected
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
n/a	Packaging	packaging workflow not detected
10	Pinned-Dependencies	all dependencies are pinned
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
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
8	Vulnerabilities	2 existing vulnerabilities detected

Direct dependencies 7

Registry	Package	Version constraint	Manifest
npm	arg	`5.0.2`	package.json
npm	check-more-types	`2.24.0`	package.json
npm	debug	`4.4.3`	package.json
npm	execa	`5.1.1`	package.json
npm	lazy-ass	`2.0.3`	package.json
npm	tree-kill	`1.2.2`	package.json
npm	wait-on	`9.1.0`	package.json

All dependencies 210

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

Registry	Package	Version	Relation
npm	arg	`5.0.2`	direct
npm	check-more-types	`2.24.0`	direct
npm	debug	`2.6.9`	direct
npm	debug	`3.1.0`	direct
npm	debug	`4.4.3`	direct
npm	execa	`5.1.1`	direct
npm	lazy-ass	`2.0.3`	direct
npm	tree-kill	`1.2.2`	direct
npm	wait-on	`9.1.0`	direct
npm	@epic-web/invariant	`1.0.0`	indirect
npm	@hapi/address	`5.1.1`	indirect
npm	@hapi/formula	`3.0.2`	indirect
npm	@hapi/hoek	`11.0.7`	indirect
npm	@hapi/pinpoint	`2.0.1`	indirect
npm	@hapi/tlds	`1.1.7`	indirect
npm	@hapi/topo	`6.0.2`	indirect
npm	@sinonjs/commons	`3.0.1`	indirect
npm	@sinonjs/fake-timers	`15.4.0`	indirect
npm	@sinonjs/samsam	`10.0.2`	indirect
npm	@standard-schema/spec	`1.1.0`	indirect
npm	@types/node	`25.9.5`	indirect
npm	accepts	`1.3.8`	indirect
npm	agent-base	`6.0.2`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	argparse	`2.0.1`	indirect
npm	array-flatten	`1.1.1`	indirect
npm	assertion-error	`1.1.0`	indirect
npm	asynckit	`0.4.0`	indirect
npm	axios	`1.20.0`	indirect
npm	balanced-match	`4.0.4`	indirect
npm	basic-auth	`2.0.1`	indirect
npm	body-parser	`1.20.6`	indirect
npm	brace-expansion	`5.0.9`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	bytes	`3.1.2`	indirect
npm	call-bind-apply-helpers	`1.0.2`	indirect
npm	call-bound	`1.0.4`	indirect
npm	chai	`4.5.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	check-error	`1.0.3`	indirect
npm	chokidar	`5.0.0`	indirect
npm	cliui	`8.0.1`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	combined-stream	`1.0.8`	indirect
npm	compressible	`2.0.18`	indirect
npm	compression	`1.8.1`	indirect
npm	connect-pause	`0.1.1`	indirect
npm	content-disposition	`0.5.4`	indirect
npm	content-type	`1.0.5`	indirect
npm	cookie	`0.7.2`	indirect
npm	cookie-signature	`1.0.7`	indirect
npm	cors	`2.8.6`	indirect
npm	cross-env	`10.1.0`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	deep-eql	`4.1.4`	indirect
npm	delayed-stream	`1.0.0`	indirect
npm	depd	`2.0.0`	indirect
npm	destroy	`1.2.0`	indirect
npm	diff	`9.0.0`	indirect
npm	dunder-proto	`1.0.1`	indirect
npm	ee-first	`1.1.1`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	encodeurl	`2.0.0`	indirect
npm	errorhandler	`1.5.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	escalade	`3.2.0`	indirect
npm	escape-html	`1.0.3`	indirect
npm	etag	`1.8.1`	indirect
npm	express	`4.22.2`	indirect
npm	express-urlrewrite	`1.4.0`	indirect
npm	finalhandler	`1.3.2`	indirect
npm	find-up	`5.0.0`	indirect
npm	follow-redirects	`1.16.0`	indirect
npm	form-data	`4.0.6`	indirect
npm	forwarded	`0.2.0`	indirect
npm	fresh	`0.5.2`	indirect
npm	function-bind	`1.1.2`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-func-name	`2.0.2`	indirect
npm	get-intrinsic	`1.3.0`	indirect
npm	get-proto	`1.0.1`	indirect
npm	get-stream	`6.0.1`	indirect
npm	glob	`13.0.6`	indirect
npm	gopd	`1.2.0`	indirect
npm	graceful-fs	`4.2.11`	indirect
npm	has-flag	`4.0.0`	indirect
npm	has-symbols	`1.1.0`	indirect
npm	has-tostringtag	`1.0.2`	indirect
npm	hasown	`2.0.4`	indirect
npm	http-errors	`2.0.1`	indirect
npm	https-proxy-agent	`5.0.1`	indirect
npm	human-signals	`2.1.0`	indirect
npm	husky	`9.1.7`	indirect
npm	iconv-lite	`0.4.24`	indirect
npm	inherits	`2.0.4`	indirect
npm	ipaddr.js	`1.9.1`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-path-inside	`3.0.3`	indirect
npm	is-promise	`2.2.2`	indirect
npm	is-stream	`2.0.1`	indirect
npm	is-unicode-supported	`0.1.0`	indirect
npm	isarray	`0.0.1`	indirect
npm	isexe	`2.0.0`	indirect
npm	jju	`1.4.0`	indirect
npm	joi	`18.2.8`	indirect
npm	js-yaml	`5.4.1`	indirect
npm	json-parse-helpfulerror	`1.0.3`	indirect
npm	json-server	`0.17.4`	indirect
npm	locate-path	`6.0.0`	indirect
npm	lodash	`4.18.1`	indirect
npm	lodash-id	`0.14.1`	indirect
npm	loupe	`2.3.7`	indirect
npm	lowdb	`1.0.0`	indirect
npm	lru-cache	`11.5.2`	indirect
npm	math-intrinsics	`1.1.0`	indirect
npm	media-typer	`0.3.0`	indirect
npm	merge-descriptors	`1.0.3`	indirect
npm	merge-stream	`2.0.0`	indirect
npm	method-override	`3.0.0`	indirect
npm	methods	`1.1.2`	indirect
npm	mime	`1.6.0`	indirect
npm	mime-db	`1.52.0`	indirect
npm	mime-db	`1.54.0`	indirect
npm	mime-types	`2.1.35`	indirect
npm	mimic-fn	`2.1.0`	indirect
npm	minimatch	`10.2.6`	indirect
npm	minimist	`1.2.8`	indirect
npm	minipass	`7.1.3`	indirect
npm	mocha	`12.0.0`	indirect
npm	morgan	`1.12.0`	indirect
npm	ms	`2.0.0`	indirect
npm	ms	`2.1.3`	indirect
npm	nanoid	`3.3.18`	indirect
npm	negotiator	`0.6.3`	indirect
npm	negotiator	`0.6.4`	indirect
npm	npm-run-path	`4.0.1`	indirect
npm	object-assign	`4.1.1`	indirect
npm	object-inspect	`1.13.4`	indirect
npm	on-finished	`2.4.1`	indirect
npm	on-headers	`1.1.0`	indirect
npm	onetime	`5.1.2`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	parseurl	`1.3.3`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-scurry	`2.0.2`	indirect
npm	path-to-regexp	`0.1.13`	indirect
npm	path-to-regexp	`1.9.0`	indirect
npm	pathval	`1.1.1`	indirect
npm	picocolors	`1.1.1`	indirect
npm	pify	`3.0.0`	indirect
npm	please-upgrade-node	`3.2.0`	indirect
npm	pluralize	`8.0.0`	indirect
npm	prettier	`3.9.6`	indirect
npm	proxy-addr	`2.0.7`	indirect
npm	proxy-from-env	`2.1.0`	indirect
npm	qs	`6.15.3`	indirect
npm	range-parser	`1.2.1`	indirect
npm	raw-body	`2.5.3`	indirect
npm	readdirp	`5.1.1`	indirect
npm	require-directory	`2.1.1`	indirect
npm	rxjs	`7.8.2`	indirect
npm	safe-buffer	`5.1.2`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	safer-buffer	`2.1.2`	indirect
npm	semver-compare	`1.0.0`	indirect
npm	send	`0.19.2`	indirect
npm	serialize-javascript	`7.1.1`	indirect
npm	serve-static	`1.16.3`	indirect
npm	server-destroy	`1.0.1`	indirect
npm	setprototypeof	`1.2.0`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	side-channel	`1.1.1`	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	signal-exit	`3.0.7`	indirect
npm	sinon	`22.1.0`	indirect
npm	sinon-chai	`3.7.0`	indirect
npm	statuses	`2.0.2`	indirect
npm	steno	`0.4.4`	indirect
npm	string-width	`4.2.3`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-final-newline	`2.0.0`	indirect
npm	strip-json-comments	`5.0.3`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-color	`8.1.1`	indirect
npm	toidentifier	`1.0.1`	indirect
npm	tslib	`2.8.1`	indirect
npm	type-detect	`4.0.8`	indirect
npm	type-detect	`4.1.0`	indirect
npm	type-is	`1.6.18`	indirect
npm	undici-types	`7.24.6`	indirect
npm	unpipe	`1.0.0`	indirect
npm	utils-merge	`1.0.1`	indirect
npm	vary	`1.1.2`	indirect
npm	which	`2.0.2`	indirect
npm	workerpool	`10.0.3`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	y18n	`5.0.8`	indirect
npm	yargs	`17.7.3`	indirect
npm	yargs-parser	`21.1.1`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:start-server-and-test@3.0.12 pulls in 63 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