Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-06 17:16 UTC

nearform / node-test-parser

Node.js test runner report stream parser

JavaScriptMIT★ 5 stars⑂ 4 forkssince Mar 2023View on GitHub ↗

nearform/node-test-parser holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (81/100) and lowest on AI Readiness (36/100). It was last updated 1 day ago. 5 contributors account for most of its recent work.

overall / 100

Good

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

Ownership

NearformOrganization · verified domain

350 followers376 public repossince Mar 2012

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	Tags
npm	node-test-parser	3.1.0	47,796	4	411 days ago	test report

Metrics by category

Vitality

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

64Moderate · 21% of overall

Development activity

66Good

How it's scored

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

Inputs used

commits_last_year	35
human_commit_share	0.1
days_since_last_push	1
active_weeks_last_year	9

Release discipline

60Moderate

How it's scored

27/27	Ships releases — 11 releases published
7.2/36	Release recency — latest release 411 days ago
19.8/27	Release cadence — a release every ~96.5 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	11
latest_release_tag	v3.1.0
releases_from_tags	no
days_since_latest_release	411
mean_days_between_releases	96.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?

46Weak · 17% of overall

Popularity & adoption

22At Risk

How it's scored

9.8/60	Stars — 5 stars
4/25	Forks — 4 forks
8.7/15	Watchers — 37 watchers

Inputs used

forks	4
stars	5
watchers	37
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

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
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	2
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	github.com, shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

78Good

How it's scored

62.4/80	Monthly downloads — 47,796 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	node-test-parser
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	47,796
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?

81Excellent · 23% of overall

Maintainer resilience (bus factor)

77Good

How it's scored

45.9/54	Bus factor — 5 contributor(s) cover half of all commits
17.6/22.5	Commit distribution — top contributor authored 22% of commits
13.5/13.5	Contributor breadth — 16 contributors
0/10	OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0

Inputs used

bus_factor	5
contributors_sampled	16
top_contributor_share	0.217

Issue & PR responsiveness

81Excellent

How it's scored

40.7/42	Issue resolution — 97% of issues closed
18.5/30	PR acceptance — 149/242 decided PRs merged
13/13	Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
9/15	OpenSSF Scorecard: Code-Review — Found 2/3 approved changesets -- score normalized to 6

Inputs used

merged_prs	149
open_issues	1
closed_issues	32
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	1
prs_decided_30d	1
issue_closed_ratio	0.97
closed_unmerged_prs	93
first_time_authors_30d	1
first_time_prs_merged_30d	1
first_time_prs_decided_30d	1

Ownership & stewardship

93Exceptional

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
18.3/25	Owner reach — 350 followers of nearform
25/25	Track record — 376 public repos, account ~14 yr old

Inputs used

followers	350
owner_type	Organization
is_verified	yes
owner_login	nearform
public_repos	376
account_age_days	5,317

Package maintenance

71Good

How it's scored

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

Inputs used

packages	node-test-parser
ecosystems	npm
any_deprecated	no
min_days_since_publish	411

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall

Engineering practices

90Excellent

How it's scored

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

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	yes
has_linter_config	yes
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?

67Good · 16% of overall

Security posture

59Moderate

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 — 29 out of 29 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
4.5/7.5	Code-Review — Found 2/3 approved changesets -- score normalized to 6
0/2.5	Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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 0 issue activity found in the last 90 days -- score normalized to 10
0/5	Packaging — no data
1/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
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
7.5/7.5	Vulnerabilities — 0 existing vulnerabilities detected

Inputs used

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

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
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

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

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 164 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

36Weak · 4% of overall

Agent context & guidance

1Critical

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
0/40	Legible commit history — no data

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	—
agent_instruction_files	—
agent_instruction_max_bytes	—

Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

Verify loop (build / test / typecheck)

55Moderate

How it's scored

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

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	yes
typecheck_configs	—
agent_commit_share	0.01
toolchain_manifests	—
dependency_bot_commit_share	0.87

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

Inputs used

primary_language	JavaScript
largest_source_bytes	2,786
source_files_sampled	13
oversized_source_files	0

Key facts

5GitHub stars

16contributors

35commits, last 12 months

1days since last push

11releases

5bus factor

1open 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 ★ / 4 ⇿

0Stars

4Forks

2Releases

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 1Patch 0

Each point covers 3 days.

OpenSSF Scorecard 5.9 / 10

5.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-06 17:16 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	29 out of 29 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
6	Code-Review	Found 2/3 approved changesets -- score normalized to 6
0	Contributors	project has 0 contributing companies or organizations -- score normalized to 0
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 0 issue activity found in the last 90 days -- score normalized to 10
n/a	Packaging	packaging workflow not detected
2	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 2
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
10	Vulnerabilities	0 existing vulnerabilities detected

All dependencies 164

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

Registry	Package	Version	Relation
npm	@aashutoshrathi/word-wrap	`1.2.6`	indirect
npm	@babel/code-frame	`7.29.7`	indirect
npm	@babel/helper-validator-identifier	`7.29.7`	indirect
npm	@cacheable/memory	`2.2.0`	indirect
npm	@cacheable/utils	`2.5.0`	indirect
npm	@commitlint/cli	`21.2.3`	indirect
npm	@commitlint/config-conventional	`21.2.3`	indirect
npm	@commitlint/config-validator	`21.2.3`	indirect
npm	@commitlint/ensure	`21.2.3`	indirect
npm	@commitlint/execute-rule	`21.0.1`	indirect
npm	@commitlint/format	`21.2.3`	indirect
npm	@commitlint/is-ignored	`21.2.3`	indirect
npm	@commitlint/lint	`21.2.3`	indirect
npm	@commitlint/load	`21.2.3`	indirect
npm	@commitlint/message	`21.2.0`	indirect
npm	@commitlint/parse	`21.2.3`	indirect
npm	@commitlint/read	`21.2.3`	indirect
npm	@commitlint/resolve-extends	`21.2.3`	indirect
npm	@commitlint/rules	`21.2.3`	indirect
npm	@commitlint/to-lines	`21.0.1`	indirect
npm	@commitlint/top-level	`21.2.0`	indirect
npm	@commitlint/types	`21.2.3`	indirect
npm	@conventional-changelog/git-client	`3.1.2`	indirect
npm	@conventional-changelog/template	`1.4.0`	indirect
npm	@eslint-community/eslint-utils	`4.10.1`	indirect
npm	@eslint-community/regexpp	`4.12.2`	indirect
npm	@eslint/config-array	`0.23.5`	indirect
npm	@eslint/config-helpers	`0.7.0`	indirect
npm	@eslint/core	`1.2.1`	indirect
npm	@eslint/js	`10.0.1`	indirect
npm	@eslint/object-schema	`3.0.5`	indirect
npm	@eslint/plugin-kit	`0.7.3`	indirect
npm	@humanfs/core	`0.19.2`	indirect
npm	@humanfs/node	`0.16.8`	indirect
npm	@humanfs/types	`0.15.0`	indirect
npm	@humanwhocodes/module-importer	`1.0.1`	indirect
npm	@humanwhocodes/retry	`0.4.3`	indirect
npm	@keyv/bigmap	`1.3.1`	indirect
npm	@keyv/serialize	`1.1.1`	indirect
npm	@pkgr/core	`0.3.6`	indirect
npm	@simple-libs/child-process-utils	`2.0.0`	indirect
npm	@simple-libs/stream-utils	`2.0.0`	indirect
npm	@types/esrecurse	`4.3.1`	indirect
npm	@types/estree	`1.0.9`	indirect
npm	@types/json-schema	`7.0.15`	indirect
npm	@types/node	`26.6.2`	indirect
npm	acorn	`8.18.0`	indirect
npm	acorn-jsx	`5.3.2`	indirect
npm	ajv	`6.15.0`	indirect
npm	ajv	`8.20.0`	indirect
npm	ansi-regex	`6.3.0`	indirect
npm	ansi-styles	`6.2.3`	indirect
npm	argparse	`2.0.1`	indirect
npm	argue-cli	`3.2.0`	indirect
npm	balanced-match	`4.0.4`	indirect
npm	brace-expansion	`5.0.12`	indirect
npm	cacheable	`2.5.0`	indirect
npm	callsites	`3.1.0`	indirect
npm	cliui	`9.0.1`	indirect
npm	conventional-changelog-angular	`9.4.0`	indirect
npm	conventional-changelog-conventionalcommits	`10.3.0`	indirect
npm	conventional-commits-parser	`7.1.2`	indirect
npm	cosmiconfig	`9.0.2`	indirect
npm	cosmiconfig-typescript-loader	`6.3.0`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	debug	`4.4.3`	indirect
npm	deep-is	`0.1.4`	indirect
npm	emoji-regex	`10.6.0`	indirect
npm	env-paths	`2.2.1`	indirect
npm	error-ex	`1.3.4`	indirect
npm	es-toolkit	`1.52.0`	indirect
npm	escalade	`3.2.0`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	eslint	`10.11.0`	indirect
npm	eslint-config-prettier	`10.1.8`	indirect
npm	eslint-plugin-prettier	`5.5.6`	indirect
npm	eslint-scope	`9.1.2`	indirect
npm	eslint-visitor-keys	`3.4.3`	indirect
npm	eslint-visitor-keys	`5.0.1`	indirect
npm	espree	`11.2.0`	indirect
npm	esquery	`1.7.0`	indirect
npm	esrecurse	`4.3.0`	indirect
npm	estraverse	`5.3.0`	indirect
npm	esutils	`2.0.3`	indirect
npm	fast-deep-equal	`3.1.3`	indirect
npm	fast-diff	`1.3.0`	indirect
npm	fast-json-stable-stringify	`2.1.0`	indirect
npm	fast-levenshtein	`2.0.6`	indirect
npm	fast-uri	`3.1.8`	indirect
npm	file-entry-cache	`11.1.5`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat-cache	`6.1.23`	indirect
npm	flatted	`3.4.4`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-east-asian-width	`1.6.0`	indirect
npm	glob-parent	`6.0.2`	indirect
npm	global-directory	`5.0.0`	indirect
npm	globals	`17.13.0`	indirect
npm	hashery	`1.5.1`	indirect
npm	hookified	`1.15.1`	indirect
npm	hookified	`2.2.0`	indirect
npm	husky	`9.1.7`	indirect
npm	ignore	`5.3.2`	indirect
npm	import-fresh	`3.3.1`	indirect
npm	imurmurhash	`0.1.4`	indirect
npm	ini	`6.0.0`	indirect
npm	is-arrayish	`0.2.1`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-plain-obj	`4.1.0`	indirect
npm	isexe	`2.0.0`	indirect
npm	jiti	`2.6.1`	indirect
npm	js-tokens	`4.0.0`	indirect
npm	js-yaml	`4.3.2`	indirect
npm	json-parse-even-better-errors	`2.3.1`	indirect
npm	json-schema-traverse	`0.4.1`	indirect
npm	json-schema-traverse	`1.0.0`	indirect
npm	json-stable-stringify-without-jsonify	`1.0.1`	indirect
npm	keyv	`5.6.0`	indirect
npm	levn	`0.4.1`	indirect
npm	lines-and-columns	`1.2.4`	indirect
npm	lint-staged	`17.6.0`	indirect
npm	locate-path	`6.0.0`	indirect
npm	minimatch	`10.2.6`	indirect
npm	ms	`2.1.3`	indirect
npm	natural-compare	`1.4.0`	indirect
npm	optionator	`0.9.3`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	parent-module	`1.0.1`	indirect
npm	parse-json	`5.2.0`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	picocolors	`1.1.1`	indirect
npm	picomatch	`4.0.7`	indirect
npm	prelude-ls	`1.2.1`	indirect
npm	prettier	`3.9.9`	indirect
npm	prettier-linter-helpers	`1.0.1`	indirect
npm	punycode	`2.3.1`	indirect
npm	qified	`0.10.1`	indirect
npm	require-from-string	`2.0.2`	indirect
npm	resolve-from	`4.0.0`	indirect
npm	resolve-from	`5.0.0`	indirect
npm	semver	`7.8.5`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	string-argv	`0.3.2`	indirect
npm	string-width	`7.2.0`	indirect
npm	string-width	`8.2.2`	indirect
npm	strip-ansi	`7.2.0`	indirect
npm	synckit	`0.11.13`	indirect
npm	tinyexec	`1.3.1`	indirect
npm	tstyche	`7.2.5`	indirect
npm	type-check	`0.4.0`	indirect
npm	typescript	`5.8.3`	indirect
npm	undici-types	`8.9.0`	indirect
npm	uri-js	`4.4.1`	indirect
npm	which	`2.0.2`	indirect
npm	wrap-ansi	`9.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yaml	`2.9.1`	indirect
npm	yargs	`18.1.0`	indirect
npm	yargs-parser	`22.0.0`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 164 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

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