Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-07 23:22 UTC

adamgruber / mochawesome

A Gorgeous HTML/CSS Reporter for Mocha.js

JavaScriptMIT★ 1,080 stars⑂ 166 forkssince Feb 2015View on GitHub ↗

adamgruber/mochawesome holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (90/100) and lowest on AI Readiness (45/100). It was last updated 38 days ago. A single contributor accounts 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 68 is calibrated to 80 on the published index scale (record calibration 2026-08-02).

Ownership

Adam GruberPersonal account

134 followers70 public repossince Sep 2012Prime Video

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	mochawesome	8.0.1	4,978,652	68	38 days ago	mocha reporter json html

Metrics by category

Vitality

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

61Moderate · 21% of overall

Development activity

45Weak

How it's scored

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

Inputs used

commits_last_year	29
human_commit_share	0.98
days_since_last_push	38
active_weeks_last_year	5

Release discipline

84Excellent

How it's scored

27/27	Ships releases — 59 releases published
36/36	Release recency — latest release 38 days ago
12.6/27	Release cadence — a release every ~221.2 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	59
latest_release_tag	8.0.1
releases_from_tags	no
days_since_latest_release	38
mean_days_between_releases	221.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?

80Excellent · 17% of overall

Popularity & adoption

75Good

How it's scored

49.2/60	Stars — 1,080 stars
18.5/25	Forks — 166 forks
7.4/15	Watchers — 22 watchers

Inputs used

forks	166
stars	1,080
watchers	22
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

70Good

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
18/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	3
has_contributing	yes
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	github.com, shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 4,978,652 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	mochawesome
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	4,978,652
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?

59Moderate · 23% of overall

Maintainer resilience (bus factor)

27At Risk

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
1.2/22.5	Commit distribution — top contributor authored 95% of commits
13.5/13.5	Contributor breadth — 10 contributors
3/10	OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3

Inputs used

bus_factor	1
contributors_sampled	10
top_contributor_share	0.947

Issue & PR responsiveness

62Moderate

How it's scored

30.4/42	Issue resolution — 72% of issues closed
23.2/30	PR acceptance — 96/124 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/11 approved changesets -- score normalized to 0

Inputs used

merged_prs	96
open_issues	80
closed_issues	211
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.725
closed_unmerged_prs	28
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

63Moderate

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
15.3/25	Owner reach — 134 followers of adamgruber
25/25	Track record — 70 public repos, account ~13 yr old

Inputs used

followers	134
owner_type	User
is_verified	—
owner_login	adamgruber
public_repos	70
account_age_days	5,101

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

Inputs used

packages	mochawesome
ecosystems	npm
any_deprecated	no
min_days_since_publish	38

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall

Engineering practices

84Excellent

How it's scored

24/24	CI workflows — 2 workflow(s)
24/24	Tests present
16/16	Linter config — eslint.config.js, package.json ("prettier")
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
20/20	OpenSSF Scorecard: CI-Tests — 6 out of 6 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	yes
has_precommit_config	no

Documentation

100Exceptional

How it's scored

30/30	README
25/25	Documentation directory
15/15	Documentation / homepage site — https://gitter.im/mochawesome/general
10/10	Repository description
10/10	Topics — 4 topics
10/10	Wiki

Inputs used

topics	mocha, reporter, mocha-reporter, tdd
has_wiki	yes
homepage	https://gitter.im/mochawesome/general
docs_site	https://gitter.im/mochawesome/general
has_readme	yes
has_docs_dir	yes
has_description	yes

Security

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

54Moderate · 16% of overall

Security posture

42Weak

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
2.2/7.5	Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5	CI-Tests — 6 out of 6 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/11 approved changesets -- score normalized to 0
0.8/2.5	Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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
7.5/7.5	Maintained — 27 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
5/5	Packaging — packaging workflow detected
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
2.2/7.5	Vulnerabilities — 7 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	17
scorecard_version	v5.5.0
checks_inconclusive	1
scorecard_aggregate	4.2

Excluded from scoring (no data or not applicable): 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	38
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:mochawesome@8.0.1 runtime dependency closure — what installing the published package pulls in — 38 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.

45Weak · 4% of overall

Agent context & guidance

26At Risk

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.49
agent_instruction_files	—
agent_instruction_max_bytes	—

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, package.json ("prettier")
0/11	Static type checking
10/10	Reproducible environment — lockfile
10/10	Demonstrated agent practice — 19 of the last 100 commits agent-authored or agent-credited
0/8	Automated maintenance — no automated dependency updates observed
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.19
toolchain_manifests	—
dependency_bot_commit_share	0

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

Inputs used

primary_language	JavaScript
largest_source_bytes	13,441
source_files_sampled	31
oversized_source_files	0

Key facts

1,080GitHub stars

10contributors

29commits, last 12 months

38days since last push

59releases

1bus factor

80open 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 ★ / 166 ⇿

0Stars

166Forks

51Releases

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 6Minor 13Patch 32

Each point covers 11 days.

OpenSSF Scorecard 4.2 / 10

4.2aggregate

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-07 23:22 UTC

10	Binary-Artifacts	no binaries found in the repo
3	Branch-Protection	branch protection is not maximal on development and all release branches
10	CI-Tests	6 out of 6 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/11 approved changesets -- score normalized to 0
3	Contributors	project has 1 contributing companies or organizations -- score normalized to 3
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
10	Maintained	27 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
10	Packaging	packaging workflow 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
3	Vulnerabilities	7 existing vulnerabilities detected

Direct dependencies 3

Registry	Package	Version constraint	Manifest
npm	diff	`^5.2.0`	package.json
npm	json-stringify-safe	`^5.0.1`	package.json
npm	mochawesome-report-generator	`^6.3.2`	package.json

All dependencies 219

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

Registry	Package	Version	Relation
npm	diff	`5.2.2`	direct
npm	diff	`7.0.0`	direct
npm	diff	`9.0.0`	direct
npm	json-stringify-safe	`5.0.1`	direct
npm	mochawesome-report-generator	`6.3.2`	direct
npm	@bcoe/v8-coverage	`1.0.2`	indirect
npm	@eslint-community/eslint-utils	`4.9.1`	indirect
npm	@eslint-community/regexpp	`4.12.2`	indirect
npm	@eslint/config-array	`0.23.5`	indirect
npm	@eslint/config-helpers	`0.6.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.2`	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	@isaacs/cliui	`8.0.2`	indirect
npm	@istanbuljs/schema	`0.1.6`	indirect
npm	@jridgewell/resolve-uri	`3.1.2`	indirect
npm	@jridgewell/sourcemap-codec	`1.5.5`	indirect
npm	@jridgewell/trace-mapping	`0.3.31`	indirect
npm	@pkgjs/parseargs	`0.11.0`	indirect
npm	@sinonjs/commons	`3.0.1`	indirect
npm	@sinonjs/fake-timers	`15.4.0`	indirect
npm	@sinonjs/samsam	`10.0.2`	indirect
npm	@types/esrecurse	`4.3.1`	indirect
npm	@types/estree	`1.0.9`	indirect
npm	@types/istanbul-lib-coverage	`2.0.6`	indirect
npm	@types/json-schema	`7.0.15`	indirect
npm	acorn	`8.17.0`	indirect
npm	acorn-jsx	`5.3.2`	indirect
npm	ajv	`6.15.0`	indirect
npm	ansi-escapes	`7.3.0`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-regex	`6.2.2`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	ansi-styles	`6.2.3`	indirect
npm	argparse	`2.0.1`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	balanced-match	`4.0.4`	indirect
npm	brace-expansion	`2.1.1`	indirect
npm	brace-expansion	`5.0.7`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	c8	`11.0.0`	indirect
npm	camelcase	`6.2.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	chokidar	`4.0.3`	indirect
npm	cli-cursor	`5.0.0`	indirect
npm	cli-truncate	`5.2.0`	indirect
npm	cliui	`8.0.1`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	convert-source-map	`2.0.0`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	dateformat	`4.6.3`	indirect
npm	debug	`4.4.3`	indirect
npm	decamelize	`4.0.0`	indirect
npm	deep-is	`0.1.4`	indirect
npm	eastasianwidth	`0.2.0`	indirect
npm	emoji-regex	`10.6.0`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	emoji-regex	`9.2.2`	indirect
npm	environment	`1.1.0`	indirect
npm	escalade	`3.2.0`	indirect
npm	escape-html	`1.0.3`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	eslint	`10.6.0`	indirect
npm	eslint-config-prettier	`10.1.8`	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	eventemitter3	`5.0.4`	indirect
npm	fast-deep-equal	`3.1.3`	indirect
npm	fast-json-stable-stringify	`2.1.0`	indirect
npm	fast-levenshtein	`2.0.6`	indirect
npm	file-entry-cache	`8.0.0`	indirect
npm	fill-keys	`1.0.2`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat	`5.0.2`	indirect
npm	flat-cache	`4.0.1`	indirect
npm	flatted	`3.4.2`	indirect
npm	foreground-child	`3.3.1`	indirect
npm	fs-extra	`10.0.0`	indirect
npm	fsu	`1.1.1`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-east-asian-width	`1.6.0`	indirect
npm	glob	`10.5.0`	indirect
npm	glob	`13.0.6`	indirect
npm	glob-parent	`6.0.2`	indirect
npm	globals	`17.7.0`	indirect
npm	graceful-fs	`4.2.3`	indirect
npm	has-flag	`4.0.0`	indirect
npm	he	`1.2.0`	indirect
npm	html-escaper	`2.0.2`	indirect
npm	husky	`9.1.7`	indirect
npm	ignore	`5.3.2`	indirect
npm	imurmurhash	`0.1.4`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-fullwidth-code-point	`5.1.0`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-object	`1.0.1`	indirect
npm	is-path-inside	`3.0.3`	indirect
npm	is-plain-obj	`2.1.0`	indirect
npm	is-unicode-supported	`0.1.0`	indirect
npm	isexe	`2.0.0`	indirect
npm	istanbul-lib-coverage	`3.2.2`	indirect
npm	istanbul-lib-report	`3.0.1`	indirect
npm	istanbul-reports	`3.2.0`	indirect
npm	jackspeak	`3.4.3`	indirect
npm	js-tokens	`4.0.0`	indirect
npm	js-yaml	`4.3.0`	indirect
npm	json-buffer	`3.0.1`	indirect
npm	json-schema-traverse	`0.4.1`	indirect
npm	json-stable-stringify-without-jsonify	`1.0.1`	indirect
npm	jsonfile	`6.1.0`	indirect
npm	keyv	`4.5.4`	indirect
npm	levn	`0.4.1`	indirect
npm	lint-staged	`17.0.8`	indirect
npm	listr2	`10.2.2`	indirect
npm	locate-path	`6.0.0`	indirect
npm	lodash.isfunction	`3.0.9`	indirect
npm	log-symbols	`4.1.0`	indirect
npm	log-update	`6.1.0`	indirect
npm	loose-envify	`1.4.0`	indirect
npm	lru-cache	`10.4.3`	indirect
npm	lru-cache	`11.5.1`	indirect
npm	make-dir	`4.0.0`	indirect
npm	merge-descriptors	`1.0.1`	indirect
npm	mimic-function	`5.0.1`	indirect
npm	minimatch	`10.2.5`	indirect
npm	minimatch	`9.0.9`	indirect
npm	minipass	`7.1.3`	indirect
npm	mocha	`11.7.6`	indirect
npm	module-not-found-error	`1.0.1`	indirect
npm	ms	`2.1.3`	indirect
npm	natural-compare	`1.4.0`	indirect
npm	object-assign	`4.1.1`	indirect
npm	onetime	`7.0.0`	indirect
npm	opener	`1.5.2`	indirect
npm	optionator	`0.9.4`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	package-json-from-dist	`1.0.1`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-parse	`1.0.7`	indirect
npm	path-scurry	`1.11.1`	indirect
npm	path-scurry	`2.0.2`	indirect
npm	picocolors	`1.1.1`	indirect
npm	picomatch	`4.0.4`	indirect
npm	prelude-ls	`1.2.1`	indirect
npm	prettier	`3.9.4`	indirect
npm	prop-types	`15.7.2`	indirect
npm	proxyquire	`2.1.3`	indirect
npm	punycode	`2.3.1`	indirect
npm	randombytes	`2.1.0`	indirect
npm	react-is	`16.13.1`	indirect
npm	readdirp	`4.1.2`	indirect
npm	require-directory	`2.1.1`	indirect
npm	resolve	`1.15.1`	indirect
npm	restore-cursor	`5.1.0`	indirect
npm	rfdc	`1.4.1`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	semver	`7.8.5`	indirect
npm	serialize-javascript	`6.0.2`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	should	`13.2.3`	indirect
npm	should-equal	`2.0.0`	indirect
npm	should-format	`3.0.3`	indirect
npm	should-type	`1.4.0`	indirect
npm	should-type-adaptors	`1.1.0`	indirect
npm	should-util	`1.0.1`	indirect
npm	signal-exit	`4.1.0`	indirect
npm	sinon	`22.0.0`	indirect
npm	slice-ansi	`7.1.2`	indirect
npm	slice-ansi	`8.0.0`	indirect
npm	string-argv	`0.3.2`	indirect
npm	string-width	`4.2.3`	indirect
npm	string-width	`5.1.2`	indirect
npm	string-width	`7.2.0`	indirect
npm	string-width	`8.2.1`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-ansi	`7.2.0`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-color	`8.1.1`	indirect
npm	tcomb	`3.2.29`	indirect
npm	tcomb-validation	`3.4.1`	indirect
npm	test-exclude	`8.0.0`	indirect
npm	tinyexec	`1.2.4`	indirect
npm	type-check	`0.4.0`	indirect
npm	type-detect	`4.0.8`	indirect
npm	type-detect	`4.1.0`	indirect
npm	universalify	`2.0.0`	indirect
npm	uri-js	`4.4.1`	indirect
npm	v8-to-istanbul	`9.3.0`	indirect
npm	which	`2.0.2`	indirect
npm	word-wrap	`1.2.5`	indirect
npm	workerpool	`9.3.4`	indirect
npm	wrap-ansi	`10.0.0`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrap-ansi	`8.1.0`	indirect
npm	wrap-ansi	`9.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yaml	`2.9.0`	indirect
npm	yargs	`17.7.3`	indirect
npm	yargs-parser	`21.1.1`	indirect
npm	yargs-unparser	`2.0.0`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:mochawesome@8.0.1 pulls in 38 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