Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 17:14 UTC

test-runner-js / test-runner

Fully-featured, lightweight command-line test runner

JavaScriptMIT★ 2 stars⑂ 1 forksince Jul 2018View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

test-runner-js/test-runner holds a health index of 50 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (82/100) and lowest on AI Readiness (30/100). It was last updated 32 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

test-runner-jsOrganization
0 followers11 public repossince Nov 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmtest-runner0.11.13,64095754 days agotest-runnertestrunnercliunittestingtooltapetapavamocha

Metrics by category

Vitality

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

43Weak · 21% of overall
How it's scored
18/36Push recency — last push 32 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push32
active_weeks_last_year0
How it's scored
16.2/27Ships releases — 62 version tags (no GitHub releases)
36/36Release recency — latest release 32 days ago
19.8/27Release cadence — a release every ~87.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count62
latest_release_tagv0.12.0-10
releases_from_tagsyes
days_since_latest_release32
mean_days_between_releases87.6
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?

33At Risk · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars2
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadgen.net, github.com, shields.io
has_pull_request_templateno
How it's scored
47.5/80Monthly downloads — 3,640 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestest-runner
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads3,640
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?

51Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution — 100% of issues closed
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
0/25Owner reach — 0 followers of test-runner-js
19.9/25Track record — 11 public repos, account ~7 yr old
Inputs used
followers0
owner_typeOrganization
is_verifiedno
owner_logintest-runner-js
public_repos11
account_age_days2,917
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 754 days ago
20/20Version history — 95 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestest-runner
ecosystemsnpm
any_deprecatedno
min_days_since_publish754

Engineering Quality

Are baseline engineering and documentation practices in place?

82Excellent · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — package.json ("standard")
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 8 topics
10/10Wiki
Inputs used
topicsdev-tools, command-line, dev-tool, test, testing, testing-tool, test-runner, nodejs
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?

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 39 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate2.5
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages52
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:test-runner@0.11.1 runtime dependency closure — what installing the published package pulls in — 52 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.

30At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — 0 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — package.json ("standard")
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/27 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes7,971
source_files_sampled27
oversized_source_files0

Key facts

2GitHub stars
1contributors
0commits, last 12 months
32days since last push
62releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 2.5 / 10
2.5aggregate

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-11-21 17:14 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities39 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
npm@test-runner/core^0.10.0package.json
npm@test-runner/default-view^0.6.1package.json
npm@test-runner/live-view^0.2.1package.json
npm@test-runner/oneline-view^0.2.0package.json
npm@test-runner/tom^0.9.1package.json
npmcommand-line-args^6.0.0package.json
npmcommand-line-usage^7.0.3package.json
npmcurrent-module-paths^1.1.1package.json
npmfast-glob^3.3.2package.json
npmload-module^4.2.1package.json
npmwalk-back^5.1.0package.json
All dependencies 148

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

RegistryPackageVersionRelation
npm@test-runner/core0.10.0direct
npm@test-runner/default-view0.6.1direct
npm@test-runner/live-view0.2.1direct
npm@test-runner/oneline-view0.2.0direct
npm@test-runner/tom0.8.1direct
npm@test-runner/tom0.9.1direct
npmcommand-line-args5.2.1direct
npmcommand-line-args6.0.0direct
npmcommand-line-usage4.1.0direct
npmcommand-line-usage7.0.3direct
npmcurrent-module-paths1.1.1direct
npmfast-glob3.3.2direct
npmload-module4.2.1direct
npmwalk-back2.0.1direct
npmwalk-back5.1.0direct
npm@75lb/deep-merge1.1.1indirect
npm@babel/parser7.24.8indirect
npm@jsdoc/salty0.2.8indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@types/linkify-it5.0.0indirect
npm@types/markdown-it14.1.1indirect
npm@types/mdurl2.0.0indirect
npmansi-escape-sequences4.1.0indirect
npmansi-escape-sequences6.2.0indirect
npmansi-regex6.0.1indirect
npmansi-styles4.3.0indirect
npmargparse2.0.1indirect
npmarray-back1.0.4indirect
npmarray-back2.0.0indirect
npmarray-back3.1.0indirect
npmarray-back4.0.2indirect
npmarray-back5.0.0indirect
npmarray-back6.2.2indirect
npmbalanced-match1.0.2indirect
npmbluebird3.7.2indirect
npmbrace-expansion1.1.11indirect
npmbraces3.0.3indirect
npmcache-point2.0.0indirect
npmcatharsis0.9.0indirect
npmchalk4.1.2indirect
npmchalk-template0.4.0indirect
npmchar-regex2.0.0indirect
npmcollect-all1.0.4indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcommand-line-tool0.8.0indirect
npmcommon-sequence2.0.2indirect
npmcomposite-class2.0.1indirect
npmconcat-map0.0.1indirect
npmconfig-master3.1.0indirect
npmcreate-mixin3.0.0indirect
npmdata-uri-to-buffer4.0.0indirect
npmdeep-extend0.6.0indirect
npmdmd6.2.0indirect
npmentities4.5.0indirect
npmescape-string-regexp2.0.0indirect
npmfastq1.17.1indirect
npmfetch-blob3.2.0indirect
npmfile-set4.0.2indirect
npmfill-range7.1.1indirect
npmfind-replace3.0.0indirect
npmfind-replace5.0.1indirect
npmformdata-polyfill4.0.10indirect
npmfs-then-native2.0.0indirect
npmfs.realpath1.0.0indirect
npmfsm-base0.7.0indirect
npmglob7.2.0indirect
npmglob-parent5.1.2indirect
npmgraceful-fs4.2.11indirect
npmhandlebars4.7.8indirect
npmhas-flag4.0.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmjs2xmlparser4.0.2indirect
npmjsdoc4.0.3indirect
npmjsdoc-api8.0.0indirect
npmjsdoc-parse6.2.1indirect
npmjsdoc-to-markdown8.0.1indirect
npmklaw3.0.0indirect
npmlinkify-it5.0.0indirect
npmlodash4.17.21indirect
npmlodash.assignwith4.2.0indirect
npmlodash.camelcase4.3.0indirect
npmlodash.omit4.5.0indirect
npmlodash.padend4.6.1indirect
npmmarkdown-it14.1.0indirect
npmmarkdown-it-anchor8.6.7indirect
npmmarked4.3.0indirect
npmmdurl2.0.0indirect
npmmerge21.4.1indirect
npmmicromatch4.0.7indirect
npmminimatch3.0.4indirect
npmminimist1.2.8indirect
npmmkdirp1.0.4indirect
npmmkdirp21.0.5indirect
npmneo-async2.6.2indirect
npmnode-domexception1.0.0indirect
npmnode-fetch3.3.2indirect
npmobject-get2.1.1indirect
npmobject-to-spawn-args2.0.1indirect
npmobso0.7.0indirect
npmonce1.4.0indirect
npmpath-is-absolute1.0.1indirect
npmpicomatch2.3.1indirect
npmpunycode.js2.3.1indirect
npmqueue-microtask1.2.3indirect
npmrace-timeout-anywhere2.0.0indirect
npmreduce-extract1.0.0indirect
npmreduce-flatten1.0.1indirect
npmreduce-flatten3.0.1indirect
npmreduce-unique2.0.1indirect
npmreduce-without1.0.1indirect
npmrequizzle0.2.4indirect
npmreusify1.0.4indirect
npmrun-parallel1.2.0indirect
npmsort-array4.1.5indirect
npmsource-map0.6.1indirect
npmstream-connect1.0.2indirect
npmstream-via1.0.4indirect
npmstring-length5.0.1indirect
npmstrip-ansi7.0.1indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmtable-layout0.4.5indirect
npmtable-layout4.1.0indirect
npmtemp-path1.0.0indirect
npmtest-value1.1.0indirect
npmtest-value2.1.0indirect
npmtest-value3.0.0indirect
npmto-regex-range5.0.1indirect
npmtypical2.6.1indirect
npmtypical4.0.0indirect
npmtypical6.0.1indirect
npmtypical7.1.1indirect
npmuc.micro2.1.0indirect
npmuglify-js3.19.0indirect
npmunderscore1.13.6indirect
npmweb-streams-polyfill3.2.0indirect
npmwordwrap1.0.0indirect
npmwordwrapjs3.0.0indirect
npmwordwrapjs5.1.0indirect
npmwrappy1.0.2indirect
npmxmlcreate2.0.4indirect
Dependency advisories 0

Installing npm:test-runner@0.11.1 pulls in 52 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 statistics — npm.