Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 08:03 UTC

semantic-release / error

💥 💬 errors but with error code

JavaScriptMIT★ 12 stars⑂ 6 forkssince Jul 2015View on GitHub ↗

semantic-release/error holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Security (78/100) and lowest on AI Readiness (39/100). It was last updated 1 day ago. 2 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 60 is calibrated to 65 on the published index scale (record calibration 2026-08-02).

Ownership

Semantic ReleaseOrganization

406 followers37 public repossince Jun 2015

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	@semantic-release/error	4.0.0	23,512,972	8	1195 days ago	error semantic-release

Metrics by category

Vitality

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

43Weak · 21% of overall

Development activity

47Weak

How it's scored

36/36	Push recency — last push 1 days ago
0.8/36	Commit cadence — 44/52 weeks with commits, discounted for automation: 1 of the last 100 commits human-authored, spanning 170 days
0.4/18	Commit volume — 81 commits in the last year, discounted for automation: 1 of the last 100 commits human-authored, spanning 170 days
10/10	OpenSSF Scorecard: Maintained — 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	81
human_commit_share	0.01
days_since_last_push	1
active_weeks_last_year	44

Release discipline

36Weak

How it's scored

27/27	Ships releases — 8 releases published
0/36	Release recency — latest release 1,195 days ago
5.4/27	Release cadence — a release every ~392.8 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	8
latest_release_tag	v4.0.0
releases_from_tags	no
days_since_latest_release	1,195
mean_days_between_releases	392.8

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?

52Moderate · 17% of overall

Popularity & adoption

23At Risk

How it's scored

16.9/60	Stars — 12 stars
5.8/25	Forks — 6 forks
0/15	Watchers — 2 watchers

Inputs used

forks	6
stars	12
watchers	2
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	1
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	github.com
has_pull_request_template	no

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 23,512,972 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	@semantic-release/error
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	23,512,972
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?

71Good · 23% of overall

Maintainer resilience (bus factor)

61Moderate

How it's scored

25.2/54	Bus factor — 2 contributor(s) cover half of all commits
15.3/22.5	Commit distribution — top contributor authored 32% of commits
10.8/13.5	Contributor breadth — 8 contributors
10/10	OpenSSF Scorecard: Contributors — project has 23 contributing companies or organizations

Inputs used

bus_factor	2
contributors_sampled	8
top_contributor_share	0.321

Issue & PR responsiveness

85Excellent

How it's scored

35.5/42	Issue resolution — 85% of issues closed
25.5/30	PR acceptance — 411/483 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — no data

Inputs used

merged_prs	411
open_issues	2
closed_issues	11
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.846
closed_unmerged_prs	72
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, OpenSSF Scorecard: Code-Review. Remaining weights renormalized.

Ownership & stewardship

72Good

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
18.8/25	Owner reach — 406 followers of semantic-release
23.5/25	Track record — 37 public repos, account ~11 yr old

Inputs used

followers	406
owner_type	Organization
is_verified	no
owner_login	semantic-release
public_repos	37
account_age_days	4,112

Package maintenance

69Good

How it's scored

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

Inputs used

packages	@semantic-release/error
ecosystems	npm
any_deprecated	no
min_days_since_publish	1,195

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall

Engineering practices

64Moderate

How it's scored

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

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	yes
has_precommit_config	no

Documentation

65Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://www.npmjs.com/package/@semantic-release/error
10/10	Repository description
10/10	Topics — 2 topics
0/10	Wiki

Inputs used

topics	semantic-release, error
has_wiki	no
homepage	https://www.npmjs.com/package/@semantic-release/error
docs_site	https://www.npmjs.com/package/@semantic-release/error
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?

78Good · 16% of overall

Security posture

73Good

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
0/2.5	CI-Tests — 0 out of 30 merged PRs checked by a CI test -- score normalized to 0
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — no data
2.5/2.5	Contributors — project has 23 contributing companies or organizations
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 — 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5	Packaging — packaging workflow detected
5/5	Pinned-Dependencies — all dependencies are pinned
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
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
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	7.3

Excluded from scoring (no data or not applicable): Branch-Protection, Code-Review, 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	170
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 170 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.

39Weak · 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)

61Moderate

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
11/11	Lint / format config — package.json ("prettier")
0/11	Static type checking
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
8/8	Automated maintenance — 99 of the last 100 commits are automated dependency updates
10/10	OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned

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
toolchain_manifests	—
dependency_bot_commit_share	0.99

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

Inputs used

primary_language	JavaScript
largest_source_bytes	1,941
source_files_sampled	5
oversized_source_files	0

Key facts

12GitHub stars

8contributors

81commits, last 12 months

1days since last push

8releases

2bus factor

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

0Stars

6Forks

3Releases

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 2Minor 0Patch 0

Each point covers 6 days.

OpenSSF Scorecard 7.3 / 10

7.3aggregate

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-15 08:02 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
0	CI-Tests	0 out of 30 merged PRs checked by a CI test -- score normalized to 0
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
n/a	Code-Review	Found no human activity in the last 30 changesets
10	Contributors	project has 23 contributing companies or organizations
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	23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10	Packaging	packaging workflow detected
10	Pinned-Dependencies	all dependencies are pinned
0	SAST	SAST tool is not run on all commits -- score normalized to 0
10	Security-Policy	security policy file 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 170

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

Registry	Package	Version	Relation
npm	@bcoe/v8-coverage	`1.0.2`	indirect
npm	@cto.af/wtf8	`0.0.5`	indirect
npm	@isaacs/fs-minipass	`4.0.1`	indirect
npm	@istanbuljs/schema	`0.1.6`	indirect
npm	@jridgewell/resolve-uri	`3.1.2`	indirect
npm	@jridgewell/sourcemap-codec	`1.6.0`	indirect
npm	@jridgewell/trace-mapping	`0.3.31`	indirect
npm	@mapbox/node-pre-gyp	`2.0.3`	indirect
npm	@nodelib/fs.scandir	`2.1.5`	indirect
npm	@nodelib/fs.stat	`2.0.5`	indirect
npm	@nodelib/fs.walk	`1.2.8`	indirect
npm	@rollup/pluginutils	`5.4.0`	indirect
npm	@sindresorhus/merge-streams	`4.0.0`	indirect
npm	@types/estree	`1.0.9`	indirect
npm	@types/istanbul-lib-coverage	`2.0.6`	indirect
npm	@vercel/nft	`1.11.0`	indirect
npm	abbrev	`3.0.1`	indirect
npm	acorn	`8.18.0`	indirect
npm	acorn-import-attributes	`1.9.5`	indirect
npm	acorn-walk	`8.3.5`	indirect
npm	agent-base	`7.1.4`	indirect
npm	ansi-regex	`6.3.0`	indirect
npm	ansi-styles	`6.2.3`	indirect
npm	argparse	`1.0.10`	indirect
npm	array-find-index	`1.0.2`	indirect
npm	arrgv	`1.0.2`	indirect
npm	arrify	`3.0.0`	indirect
npm	async-sema	`3.1.1`	indirect
npm	ava	`8.0.1`	indirect
npm	balanced-match	`4.0.4`	indirect
npm	bindings	`1.5.0`	indirect
npm	blueimp-md5	`2.19.0`	indirect
npm	brace-expansion	`5.0.9`	indirect
npm	braces	`3.0.3`	indirect
npm	c8	`12.0.0`	indirect
npm	callsites	`4.2.0`	indirect
npm	cbor2	`2.3.0`	indirect
npm	chalk	`5.6.2`	indirect
npm	chownr	`3.0.0`	indirect
npm	chunkd	`2.0.1`	indirect
npm	ci-info	`4.4.0`	indirect
npm	ci-parallel-vars	`1.0.1`	indirect
npm	cli-truncate	`6.1.1`	indirect
npm	cliui	`9.0.1`	indirect
npm	code-excerpt	`4.0.0`	indirect
npm	common-path-prefix	`3.0.0`	indirect
npm	concordance	`5.0.4`	indirect
npm	consola	`3.4.2`	indirect
npm	convert-source-map	`2.0.0`	indirect
npm	convert-to-spaces	`2.0.1`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	currently-unhandled	`0.4.1`	indirect
npm	date-time	`3.1.0`	indirect
npm	debug	`4.4.3`	indirect
npm	detect-libc	`2.1.2`	indirect
npm	emittery	`2.0.0`	indirect
npm	emoji-regex	`10.6.0`	indirect
npm	escalade	`3.2.0`	indirect
npm	escape-string-regexp	`2.0.0`	indirect
npm	escape-string-regexp	`5.0.0`	indirect
npm	esprima	`4.0.1`	indirect
npm	estree-walker	`2.0.2`	indirect
npm	esutils	`2.0.3`	indirect
npm	fast-diff	`1.3.0`	indirect
npm	fast-glob	`3.3.3`	indirect
npm	fastq	`1.20.3`	indirect
npm	figures	`6.1.0`	indirect
npm	file-uri-to-path	`1.0.0`	indirect
npm	fill-range	`7.1.1`	indirect
npm	find-up	`5.0.0`	indirect
npm	find-up-simple	`1.0.1`	indirect
npm	foreground-child	`3.3.1`	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	glob-parent	`5.1.2`	indirect
npm	globby	`16.2.4`	indirect
npm	graceful-fs	`4.2.11`	indirect
npm	has-flag	`4.0.0`	indirect
npm	html-escaper	`2.0.2`	indirect
npm	https-proxy-agent	`7.0.6`	indirect
npm	ignore	`7.0.9`	indirect
npm	ignore-by-default	`2.1.0`	indirect
npm	indent-string	`5.0.0`	indirect
npm	irregular-plurals	`4.2.0`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-fullwidth-code-point	`5.1.0`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-number	`7.0.0`	indirect
npm	is-path-inside	`4.0.0`	indirect
npm	is-plain-object	`5.1.0`	indirect
npm	is-promise	`4.0.0`	indirect
npm	is-unicode-supported	`2.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	js-string-escape	`1.0.1`	indirect
npm	js-yaml	`3.15.2`	indirect
npm	load-json-file	`7.0.1`	indirect
npm	locate-path	`6.0.0`	indirect
npm	lodash	`4.18.1`	indirect
npm	lru-cache	`11.5.2`	indirect
npm	make-dir	`4.0.0`	indirect
npm	matcher	`6.0.0`	indirect
npm	md5-hex	`3.0.1`	indirect
npm	memoize	`11.0.0`	indirect
npm	merge2	`1.4.1`	indirect
npm	micromatch	`4.0.8`	indirect
npm	mimic-function	`5.0.1`	indirect
npm	minimatch	`10.2.6`	indirect
npm	minipass	`7.1.3`	indirect
npm	minizlib	`3.1.0`	indirect
npm	ms	`2.1.3`	indirect
npm	node-fetch	`2.7.0`	indirect
npm	node-gyp-build	`4.8.4`	indirect
npm	nopt	`8.1.0`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	p-map	`7.0.8`	indirect
npm	package-config	`5.0.0`	indirect
npm	parse-ms	`4.0.0`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-scurry	`2.0.2`	indirect
npm	picomatch	`2.3.2`	indirect
npm	picomatch	`4.0.7`	indirect
npm	plur	`6.0.0`	indirect
npm	prettier	`3.9.6`	indirect
npm	pretty-ms	`9.3.1`	indirect
npm	queue-microtask	`1.2.3`	indirect
npm	resolve-cwd	`3.0.0`	indirect
npm	resolve-from	`5.0.0`	indirect
npm	reusify	`1.1.0`	indirect
npm	run-parallel	`1.2.0`	indirect
npm	semver	`7.8.5`	indirect
npm	serialize-error	`7.0.1`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	signal-exit	`4.1.0`	indirect
npm	slash	`5.1.0`	indirect
npm	slice-ansi	`9.0.0`	indirect
npm	sprintf-js	`1.0.3`	indirect
npm	stack-utils	`2.0.6`	indirect
npm	string-width	`7.2.0`	indirect
npm	string-width	`8.2.2`	indirect
npm	strip-ansi	`7.2.0`	indirect
npm	supertap	`3.0.1`	indirect
npm	supports-color	`7.2.0`	indirect
npm	tar	`7.5.22`	indirect
npm	temp-dir	`3.0.0`	indirect
npm	test-exclude	`8.0.0`	indirect
npm	time-zone	`1.0.0`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	tr46	`0.0.3`	indirect
npm	type-fest	`0.13.1`	indirect
npm	unicorn-magic	`0.4.0`	indirect
npm	v8-to-istanbul	`9.3.0`	indirect
npm	webidl-conversions	`3.0.1`	indirect
npm	well-known-symbols	`2.0.0`	indirect
npm	whatwg-url	`5.0.0`	indirect
npm	which	`2.0.2`	indirect
npm	wrap-ansi	`9.0.2`	indirect
npm	write-file-atomic	`7.0.1`	indirect
npm	y18n	`5.0.8`	indirect
npm	yallist	`5.0.0`	indirect
npm	yargs	`18.1.0`	indirect
npm	yargs-parser	`21.1.1`	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 — 170 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