Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 15:29 UTC

ctrf-io / ctrf-cli

CLI tooling for CTRF

TypeScript · JavaScriptMIT★ 6 stars⑂ 2 forkssince Jun 2024View on GitHub ↗

KindCommand-line toolLibraryhow this is determined

#ctrf #test-reporting #open-standard #json-test-report #test-automation #testing

ctrf-io/ctrf-cli holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (78/100) and lowest on Community & Adoption (53/100). It was last updated 15 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 69 is calibrated to 81 on the published index scale (record calibration 2026-08-02).

Ownership

ctrf-ioOrganization · verified domain

150 followers23 public repossince Feb 2024

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	ctrf-cli	0.3.1	29,161	8	34 days ago	test testing ctrf reporter report json standard cli command-line test-results

Metrics by category

Vitality

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

78Good · 21% of overall

Development activity

68Good

How it's scored

28.8/36	Push recency — last push 15 days ago
12.5/36	Commit cadence — 18/52 weeks with commits
16.2/18	Commit volume — 63 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	63
human_commit_share	0.5
days_since_last_push	15
active_weeks_last_year	18

Release discipline

92Excellent

How it's scored

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

Inputs used

releases_count	6
latest_release_tag	v0.3.1
releases_from_tags	no
days_since_latest_release	34
mean_days_between_releases	60.4

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?

53Moderate · 17% of overall

Popularity & adoption

11Critical

How it's scored

11.3/60	Stars — 6 stars
0/25	Forks — 2 forks
0/15	Watchers — 1 watchers

Inputs used

forks	2
stars	6
watchers	1
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

85Excellent

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
18/18	CONTRIBUTING guide
13.5/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	0
has_contributing	yes
has_issue_template	no
has_code_of_conduct	yes
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

74Good

How it's scored

59.5/80	Monthly downloads — 29,161 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	ctrf-cli
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	29,161
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?

63Moderate · 23% of overall

Maintainer resilience (bus factor)

13Critical

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	1
top_contributor_share	1

Issue & PR responsiveness

76Good

How it's scored

42/42	Issue resolution — 100% of issues closed
24.3/30	PR acceptance — 60/74 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/5 approved changesets -- score normalized to 0

Inputs used

merged_prs	60
open_issues	0
closed_issues	8
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	1
closed_unmerged_prs	14
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

81Excellent

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
15.7/25	Owner reach — 150 followers of ctrf-io
15.3/25	Track record — 23 public repos, account ~2 yr old

Inputs used

followers	150
owner_type	Organization
is_verified	yes
owner_login	ctrf-io
public_repos	23
account_age_days	959

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	ctrf-cli
ecosystems	npm
any_deprecated	no
min_days_since_publish	34

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall

Engineering practices

80Excellent

How it's scored

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

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	yes
has_precommit_config	no

Documentation

75Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://ctrf.io
10/10	Repository description
10/10	Topics — 6 topics
10/10	Wiki

Inputs used

topics	ctrf, test-reporting, open-standard, json-test-report, test-automation, testing
has_wiki	yes
homepage	https://ctrf.io
docs_site	https://ctrf.io
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?

73Good · 16% of overall

Security posture

66Good

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
2/2.5	CI-Tests — 26 out of 29 merged PRs checked by a CI test -- score normalized to 8
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/5 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
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 — 17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5	Packaging — packaging workflow detected
2.5/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
5/5	SAST — SAST tool is run on all commits
5/5	Security-Policy — security policy file detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
3.8/7.5	Vulnerabilities — 5 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	16
scorecard_version	v5.5.0
checks_inconclusive	2
scorecard_aggregate	6.6

Excluded from scoring (no data or not applicable): Branch-Protection, 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	20
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:ctrf-cli@0.3.1 runtime dependency closure — what installing the published package pulls in — 20 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.

69Good · 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 — 36 of 38 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.947
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

67Good

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
11/11	Lint / format config — biome.json
11/11	Static type checking — tsconfig.json
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 76
8/8	Automated maintenance — 38 of the last 76 commits are automated dependency updates
5/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	yes
typecheck_configs	tsconfig.json
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0.5

Code legibility for models

100Exceptional

How it's scored

45/45	Type-checkable code — TypeScript (statically typed)
55/55	Manageable file sizes — 0/19 source files over 60KB

Inputs used

primary_language	TypeScript
largest_source_bytes	9,855
source_files_sampled	19
oversized_source_files	0

Machine-readable interfaces

100Exceptional

How it's scored

0/40	API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20	MCP server — not applicable to this kind of software
40/40	Runnable examples — examples

Inputs used

example_dirs	examples
has_mcp_signal	no
api_schema_files	—
interfaces_expected_of	—

Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

6GitHub stars

1contributors

63commits, last 12 months

15days since last push

6releases

1bus factor

0open 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 ★ / 2 ⇿

0Stars

2Forks

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.

OpenSSF Scorecard 6.6 / 10

6.6aggregate

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-18 15:29 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
8	CI-Tests	26 out of 29 merged PRs checked by a CI test -- score normalized to 8
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 0/5 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
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10	Packaging	packaging workflow detected
5	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 5
10	SAST	SAST tool is run on all commits
10	Security-Policy	security policy file detected
n/a	Signed-Releases	no releases found
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
5	Vulnerabilities	5 existing vulnerabilities detected

Direct dependencies 3

Registry	Package	Version constraint	Manifest
npm	ajv	`8.20.0`	package.json
npm	ajv-formats	`3.0.1`	package.json
npm	yargs	`18.1.0`	package.json

All dependencies 177

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

Registry	Package	Version	Relation
npm	ajv	`8.20.0`	direct
npm	ajv-formats	`3.0.1`	direct
npm	yargs	`18.1.0`	direct
npm	@babel/helper-string-parser	`7.27.1`	indirect
npm	@babel/helper-validator-identifier	`7.28.5`	indirect
npm	@babel/parser	`7.29.0`	indirect
npm	@babel/types	`7.29.0`	indirect
npm	@bcoe/v8-coverage	`1.0.2`	indirect
npm	@biomejs/biome	`2.5.8`	indirect
npm	@biomejs/cli-darwin-arm64	`2.5.8`	indirect
npm	@biomejs/cli-darwin-x64	`2.5.8`	indirect
npm	@biomejs/cli-linux-arm64	`2.5.8`	indirect
npm	@biomejs/cli-linux-arm64-musl	`2.5.8`	indirect
npm	@biomejs/cli-linux-x64	`2.5.8`	indirect
npm	@biomejs/cli-linux-x64-musl	`2.5.8`	indirect
npm	@biomejs/cli-win32-arm64	`2.5.8`	indirect
npm	@biomejs/cli-win32-x64	`2.5.8`	indirect
npm	@d2t/vitest-ctrf-json-reporter	`1.3.0`	indirect
npm	@esbuild/aix-ppc64	`0.28.2`	indirect
npm	@esbuild/android-arm	`0.28.2`	indirect
npm	@esbuild/android-arm64	`0.28.2`	indirect
npm	@esbuild/android-x64	`0.28.2`	indirect
npm	@esbuild/darwin-arm64	`0.28.2`	indirect
npm	@esbuild/darwin-x64	`0.28.2`	indirect
npm	@esbuild/freebsd-arm64	`0.28.2`	indirect
npm	@esbuild/freebsd-x64	`0.28.2`	indirect
npm	@esbuild/linux-arm	`0.28.2`	indirect
npm	@esbuild/linux-arm64	`0.28.2`	indirect
npm	@esbuild/linux-ia32	`0.28.2`	indirect
npm	@esbuild/linux-loong64	`0.28.2`	indirect
npm	@esbuild/linux-mips64el	`0.28.2`	indirect
npm	@esbuild/linux-ppc64	`0.28.2`	indirect
npm	@esbuild/linux-riscv64	`0.28.2`	indirect
npm	@esbuild/linux-s390x	`0.28.2`	indirect
npm	@esbuild/linux-x64	`0.28.2`	indirect
npm	@esbuild/netbsd-arm64	`0.28.2`	indirect
npm	@esbuild/netbsd-x64	`0.28.2`	indirect
npm	@esbuild/openbsd-arm64	`0.28.2`	indirect
npm	@esbuild/openbsd-x64	`0.28.2`	indirect
npm	@esbuild/openharmony-arm64	`0.28.2`	indirect
npm	@esbuild/sunos-x64	`0.28.2`	indirect
npm	@esbuild/win32-arm64	`0.28.2`	indirect
npm	@esbuild/win32-ia32	`0.28.2`	indirect
npm	@esbuild/win32-x64	`0.28.2`	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	@oxc-project/types	`0.143.0`	indirect
npm	@rolldown/binding-android-arm64	`1.2.3`	indirect
npm	@rolldown/binding-darwin-arm64	`1.2.3`	indirect
npm	@rolldown/binding-darwin-x64	`1.2.3`	indirect
npm	@rolldown/binding-freebsd-x64	`1.2.3`	indirect
npm	@rolldown/binding-linux-arm-gnueabihf	`1.2.3`	indirect
npm	@rolldown/binding-linux-arm64-gnu	`1.2.3`	indirect
npm	@rolldown/binding-linux-arm64-musl	`1.2.3`	indirect
npm	@rolldown/binding-linux-ppc64-gnu	`1.2.3`	indirect
npm	@rolldown/binding-linux-s390x-gnu	`1.2.3`	indirect
npm	@rolldown/binding-linux-x64-gnu	`1.2.3`	indirect
npm	@rolldown/binding-linux-x64-musl	`1.2.3`	indirect
npm	@rolldown/binding-openharmony-arm64	`1.2.3`	indirect
npm	@rolldown/binding-win32-arm64-msvc	`1.2.3`	indirect
npm	@rolldown/binding-win32-x64-msvc	`1.2.3`	indirect
npm	@rolldown/pluginutils	`1.0.1`	indirect
npm	@standard-schema/spec	`1.1.0`	indirect
npm	@types/chai	`5.2.3`	indirect
npm	@types/deep-eql	`4.0.2`	indirect
npm	@types/estree	`1.0.8`	indirect
npm	@types/node	`26.2.0`	indirect
npm	@types/yargs	`17.0.35`	indirect
npm	@types/yargs-parser	`21.0.3`	indirect
npm	@typescript/typescript-aix-ppc64	`7.0.2`	indirect
npm	@typescript/typescript-darwin-arm64	`7.0.2`	indirect
npm	@typescript/typescript-darwin-x64	`7.0.2`	indirect
npm	@typescript/typescript-freebsd-arm64	`7.0.2`	indirect
npm	@typescript/typescript-freebsd-x64	`7.0.2`	indirect
npm	@typescript/typescript-linux-arm	`7.0.2`	indirect
npm	@typescript/typescript-linux-arm64	`7.0.2`	indirect
npm	@typescript/typescript-linux-loong64	`7.0.2`	indirect
npm	@typescript/typescript-linux-mips64el	`7.0.2`	indirect
npm	@typescript/typescript-linux-ppc64	`7.0.2`	indirect
npm	@typescript/typescript-linux-riscv64	`7.0.2`	indirect
npm	@typescript/typescript-linux-s390x	`7.0.2`	indirect
npm	@typescript/typescript-linux-x64	`7.0.2`	indirect
npm	@typescript/typescript-netbsd-arm64	`7.0.2`	indirect
npm	@typescript/typescript-netbsd-x64	`7.0.2`	indirect
npm	@typescript/typescript-openbsd-arm64	`7.0.2`	indirect
npm	@typescript/typescript-openbsd-x64	`7.0.2`	indirect
npm	@typescript/typescript-sunos-x64	`7.0.2`	indirect
npm	@typescript/typescript-win32-arm64	`7.0.2`	indirect
npm	@typescript/typescript-win32-x64	`7.0.2`	indirect
npm	@vitest/coverage-v8	`4.1.10`	indirect
npm	@vitest/expect	`4.1.10`	indirect
npm	@vitest/mocker	`4.1.10`	indirect
npm	@vitest/pretty-format	`4.1.10`	indirect
npm	@vitest/runner	`4.1.10`	indirect
npm	@vitest/snapshot	`4.1.10`	indirect
npm	@vitest/spy	`4.1.10`	indirect
npm	@vitest/utils	`4.1.10`	indirect
npm	ansi-regex	`6.2.2`	indirect
npm	ansi-styles	`6.2.3`	indirect
npm	assertion-error	`2.0.1`	indirect
npm	ast-v8-to-istanbul	`1.0.0`	indirect
npm	balanced-match	`4.0.4`	indirect
npm	brace-expansion	`5.0.9`	indirect
npm	chai	`6.2.2`	indirect
npm	cliui	`9.0.1`	indirect
npm	convert-source-map	`2.0.0`	indirect
npm	ctrf	`0.3.0`	indirect
npm	detect-libc	`2.1.2`	indirect
npm	emoji-regex	`10.6.0`	indirect
npm	es-module-lexer	`2.0.0`	indirect
npm	esbuild	`0.28.2`	indirect
npm	escalade	`3.2.0`	indirect
npm	estree-walker	`3.0.3`	indirect
npm	expect-type	`1.3.0`	indirect
npm	fast-deep-equal	`3.1.3`	indirect
npm	fast-uri	`3.1.5`	indirect
npm	fdir	`6.5.0`	indirect
npm	fsevents	`2.3.3`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-east-asian-width	`1.6.0`	indirect
npm	glob	`13.0.6`	indirect
npm	has-flag	`4.0.0`	indirect
npm	html-escaper	`2.0.2`	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	js-tokens	`10.0.0`	indirect
npm	json-schema-traverse	`1.0.0`	indirect
npm	lightningcss	`1.33.0`	indirect
npm	lightningcss-android-arm64	`1.33.0`	indirect
npm	lightningcss-darwin-arm64	`1.33.0`	indirect
npm	lightningcss-darwin-x64	`1.33.0`	indirect
npm	lightningcss-freebsd-x64	`1.33.0`	indirect
npm	lightningcss-linux-arm-gnueabihf	`1.33.0`	indirect
npm	lightningcss-linux-arm64-gnu	`1.33.0`	indirect
npm	lightningcss-linux-arm64-musl	`1.33.0`	indirect
npm	lightningcss-linux-x64-gnu	`1.33.0`	indirect
npm	lightningcss-linux-x64-musl	`1.33.0`	indirect
npm	lightningcss-win32-arm64-msvc	`1.33.0`	indirect
npm	lightningcss-win32-x64-msvc	`1.33.0`	indirect
npm	lru-cache	`11.2.7`	indirect
npm	magic-string	`0.30.21`	indirect
npm	magicast	`0.5.2`	indirect
npm	make-dir	`4.0.0`	indirect
npm	minimatch	`10.2.4`	indirect
npm	minipass	`7.1.3`	indirect
npm	nanoid	`3.3.18`	indirect
npm	obug	`2.1.1`	indirect
npm	path-scurry	`2.0.2`	indirect
npm	pathe	`2.0.3`	indirect
npm	picocolors	`1.1.1`	indirect
npm	picomatch	`4.0.5`	indirect
npm	postcss	`8.5.25`	indirect
npm	require-from-string	`2.0.2`	indirect
npm	rolldown	`1.2.3`	indirect
npm	semver	`7.7.4`	indirect
npm	siginfo	`2.0.0`	indirect
npm	source-map-js	`1.2.1`	indirect
npm	stackback	`0.0.2`	indirect
npm	std-env	`4.0.0`	indirect
npm	string-width	`7.2.0`	indirect
npm	string-width	`8.2.2`	indirect
npm	strip-ansi	`7.2.0`	indirect
npm	supports-color	`7.2.0`	indirect
npm	tinybench	`2.9.0`	indirect
npm	tinyexec	`1.0.2`	indirect
npm	tinyglobby	`0.2.17`	indirect
npm	tinyrainbow	`3.1.0`	indirect
npm	typescript	`7.0.2`	indirect
npm	undici-types	`8.3.0`	indirect
npm	vite	`8.2.0`	indirect
npm	vitest	`4.1.10`	indirect
npm	why-is-node-running	`2.3.0`	indirect
npm	wrap-ansi	`9.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yargs-parser	`22.0.0`	indirect

Dependency advisories 0

Installing npm:ctrf-cli@0.3.1 pulls in 20 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