Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 23:43 UTC

test-results-reporter / parser

Parse test results from JUnit, TestNG, xUnit and many more

JavaScriptMIT★ 13 stars⑂ 11 forkssince Sep 2021View on GitHub ↗

test-results-reporter/parser holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (67/100) and lowest on Community & Adoption (49/100). It was last updated 56 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

10 followers16 public repossince Sep 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmtest-results-parser0.4.7151,3534856 days agojunitxunittestngparserparsetesttestingresultsresultreportautomationmochacucumbernunitmstesttestbeats

Metrics by category

Vitality

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

64Moderate · 21% of overall
How it's scored
18/36Push recency — last push 56 days ago
6.9/36Commit cadence — 10/52 weeks with commits
12.6/18Commit volume — 24 commits in the last year
3/10OpenSSF Scorecard: Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year24
human_commit_share0.91
days_since_last_push56
active_weeks_last_year10

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 50 releases published
36/36Release recency — latest release 56 days ago
27/27Release cadence — a release every ~39.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count50
latest_release_tagv0.4.7
releases_from_tagsno
days_since_latest_release56
mean_days_between_releases39.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?

49Weak · 17% of overall
How it's scored
17.5/60Stars — 13 stars
8.3/25Forks — 11 forks
0/15Watchers — 2 watchers
Inputs used
forks11
stars13
watchers2
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_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
69.1/80Monthly downloads — 151,353 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestest-results-parser
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads151,353
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?

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.6/22.5Commit distribution — top contributor authored 57% of commits
13.5/13.5Contributor breadth — 10 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled10
top_contributor_share0.574
How it's scored
33.3/42Issue resolution — 79% of issues closed
28.9/30PR acceptance — 82/85 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 12/21 approved changesets -- score normalized to 5
Inputs used
merged_prs82
open_issues10
closed_issues38
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.792
closed_unmerged_prs3
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
7.5/25Owner reach — 10 followers of test-results-reporter
19.3/25Track record — 16 public repos, account ~5 yr old
Inputs used
followers10
owner_typeOrganization
is_verifiedno
owner_logintest-results-reporter
public_repos16
account_age_days1,893

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 56 days ago
20/20Version history — 48 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestest-results-parser
ecosystemsnpm
any_deprecatedno
min_days_since_publish56

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests — 13 out of 27 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.testbeats.com
10/10Repository description
10/10Topics — 8 topics
10/10Wiki
Inputs used
topicsparser, junit, testng, xunit, testing, cucumber, mocha, nunit
has_wikiyes
homepagehttps://www.testbeats.com
docs_sitehttps://www.testbeats.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

53Moderate · 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
1/2.5CI-Tests — 13 out of 27 merged PRs checked by a CI test -- score normalized to 4
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 12/21 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
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
2.2/7.5Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
5/5Packaging — packaging workflow detected
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
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
3.8/7.5Vulnerabilities — 5 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.1
Excluded from scoring (no data or not applicable): 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_packages11
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-results-parser@0.4.7 runtime dependency closure — what installing the published package pulls in — 11 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.

61Moderate · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 79 of 91 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.868
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes1,898
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — devcontainer, lockfile
10/10Demonstrated agent practice — 5 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontaineryes
has_linter_configno
typecheck_configs—
agent_commit_share0.05
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/34 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes19,531
source_files_sampled34
oversized_source_files0

Key facts

13GitHub stars
10contributors
24commits, last 12 months
56days since last push
50releases
1bus factor
10open 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 ★ / 11 ⇿
0Stars
11Forks
40Releases

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.

0246810121122021-122024-042026-07
Major 0Minor 1Patch 36

Each point covers 5 days.

OpenSSF Scorecard 4.1 / 10
4.1aggregate

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-18 23:43 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
4CI-Tests13 out of 27 merged PRs checked by a CI test -- score normalized to 4
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 12/21 approved changesets -- score normalized to 5
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
10Packagingpackaging workflow detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
5Vulnerabilities5 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npmfast-xml-parser^5.11.1package.json
npmglobrex^0.1.2package.json
npmhtml-escaper^3.0.3package.json
npmtotalist^3.0.1package.json
All dependencies 108

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

RegistryPackageVersionRelation
npmfast-xml-parser5.11.1direct
npmglobrex0.1.2direct
npmhtml-escaper2.0.2direct
npmhtml-escaper3.0.3direct
npmtotalist3.0.1direct
npm@bcoe/v8-coverage1.0.2indirect
npm@isaacs/cliui8.0.2indirect
npm@istanbuljs/schema0.1.6indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.6.0indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@nodable/entities3.0.0indirect
npm@pkgjs/parseargs0.11.0indirect
npm@types/istanbul-lib-coverage2.0.6indirect
npmansi-regex5.0.1indirect
npmansi-regex6.3.0indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.3indirect
npmanynum1.0.1indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion2.1.7indirect
npmbrace-expansion5.0.12indirect
npmbrowser-stdout1.3.1indirect
npmc811.0.0indirect
npmcamelcase6.3.0indirect
npmchalk4.1.2indirect
npmchokidar4.0.3indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconvert-source-map2.0.0indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdecamelize4.0.0indirect
npmdiff8.0.4indirect
npmeastasianwidth0.2.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmescalade3.2.0indirect
npmescape-string-regexp4.0.0indirect
npmfast-xml-builder1.3.1indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmforeground-child3.3.1indirect
npmget-caller-file2.0.5indirect
npmglob10.5.0indirect
npmglob13.0.6indirect
npmhas-flag4.0.0indirect
npmhe1.2.0indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-path-inside3.0.3indirect
npmis-plain-obj2.1.0indirect
npmis-unicode-supported0.1.0indirect
npmis-unsafe2.0.2indirect
npmisexe2.0.0indirect
npmistanbul-lib-coverage3.2.2indirect
npmistanbul-lib-report3.0.1indirect
npmistanbul-reports3.2.0indirect
npmjackspeak3.4.3indirect
npmjs-yaml4.3.2indirect
npmlocate-path6.0.0indirect
npmlog-symbols4.1.0indirect
npmlru-cache10.4.3indirect
npmlru-cache11.5.2indirect
npmmake-dir4.0.0indirect
npmminimatch10.2.6indirect
npmminimatch9.0.9indirect
npmminipass7.1.3indirect
npmmocha11.8.0indirect
npmms2.1.3indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-expression-matcher1.6.2indirect
npmpath-key3.1.1indirect
npmpath-scurry1.11.1indirect
npmpath-scurry2.0.2indirect
npmpicocolors1.1.1indirect
npmreaddirp4.1.2indirect
npmrequire-directory2.1.1indirect
npmsemver7.8.5indirect
npmserialize-javascript7.1.1indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.2.0indirect
npmstrip-json-comments3.1.1indirect
npmstrnum2.4.2indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmtest-exclude8.0.0indirect
npmv8-to-istanbul9.3.0indirect
npmwhich2.0.2indirect
npmworkerpool9.3.4indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi8.1.0indirect
npmxml-naming0.3.0indirect
npmy18n5.0.8indirect
npmyargs17.7.3indirect
npmyargs-parser21.1.1indirect
npmyargs-unparser2.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:test-results-parser@0.4.7 pulls in 11 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.