Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 14:01 UTC

emn178 / js-sha256

A simple SHA-256 / SHA-224 hash function for JavaScript supports UTF-8 encoding.

JavaScriptMIT★ 969 stars⑂ 264 forkssince Jan 2014View on GitHub ↗

emn178/js-sha256 holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Community & Adoption (73/100) and lowest on AI Readiness (36/100). It was last updated 15 days ago. A single contributor accounts 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

emn178Personal account

529 followers132 public repossince Feb 2013

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	js-sha256	1.0.0	20,018,025	25	31 days ago	sha sha2 sha224 sha256 hash encryption cryptography hmac

Metrics by category

Vitality

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

70Good · 21% of overall

Development activity

50Moderate

How it's scored

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

Inputs used

commits_last_year	12
human_commit_share	0.935
days_since_last_push	15
active_weeks_last_year	2

Release discipline

100Exceptional

How it's scored

27/27	Ships releases — 2 releases published
36/36	Release recency — latest release 31 days ago
27/27	Release cadence — a release every ~8.9 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	2
latest_release_tag	v1.0.0
releases_from_tags	no
days_since_latest_release	31
mean_days_between_releases	8.9

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?

73Good · 17% of overall

Popularity & adoption

76Good

How it's scored

48.4/60	Stars — 969 stars
20.2/25	Forks — 264 forks
7.1/15	Watchers — 20 watchers

Inputs used

forks	264
stars	969
watchers	20
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	4
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	coveralls.io, github.com, shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 20,018,025 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	js-sha256
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	20,018,025
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)

20At Risk

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	6
top_contributor_share	0.877

Issue & PR responsiveness

65Good

How it's scored

39.2/42	Issue resolution — 93% of issues closed
14.3/30	PR acceptance — 11/23 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15	OpenSSF Scorecard: Code-Review — Found 6/26 approved changesets -- score normalized to 2

Inputs used

merged_prs	11
open_issues	2
closed_issues	28
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.933
closed_unmerged_prs	12
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

68Good

How it's scored

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

Inputs used

followers	529
owner_type	User
is_verified	—
owner_login	emn178
public_repos	132
account_age_days	4,951

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

Inputs used

packages	js-sha256
ecosystems	npm
any_deprecated	no
min_days_since_publish	31

Engineering Quality

Are baseline engineering and documentation practices in place?

49Weak · 19% of overall

Engineering practices

48Weak

How it's scored

24/24	CI workflows — 2 workflow(s)
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — 0 out of 10 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	no
has_precommit_config	no

Documentation

50Moderate

How it's scored

30/30	README
0/25	Documentation directory
0/15	Documentation / homepage site
10/10	Repository description
0/10	Topics
10/10	Wiki

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	—
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?

56Moderate · 16% of overall

Security posture

45Weak

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
0/2.5	CI-Tests — 0 out of 10 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
1.5/7.5	Code-Review — Found 6/26 approved changesets -- score normalized to 2
0/2.5	Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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 — 12 commit(s) and 4 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
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
0/7.5	Vulnerabilities — 14 existing vulnerabilities detected

Inputs used

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

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
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	16
affected_packages	7
assessed_packages	147
unassessed_packages	0
affected_by_severity	high 6, moderate 1
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 147 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.

36Weak · 4% of overall

Agent context & guidance

15Critical

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.276
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

45Weak

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
0/11	Static type checking
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 62
8/8	Automated maintenance — 4 of the last 62 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	no
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0.065

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

Inputs used

primary_language	JavaScript
largest_source_bytes	17,836
source_files_sampled	18
oversized_source_files	0

Key facts

969GitHub stars

6contributors

12commits, last 12 months

15days since last push

2releases

1bus 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 ★ / 264 ⇿

0Stars

264Forks

1Releases

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

Each point covers 11 days.

OpenSSF Scorecard 4.5 / 10

4.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-08-27 14:01 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
0	CI-Tests	0 out of 10 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
2	Code-Review	Found 6/26 approved changesets -- score normalized to 2
0	Contributors	project has 0 contributing companies or organizations -- score normalized to 0
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	12 commit(s) and 4 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
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
0	Vulnerabilities	14 existing vulnerabilities detected

All dependencies 147

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

Registry	Package	Version	Relation
npm	@bcoe/v8-coverage	`0.2.3`	indirect
npm	@istanbuljs/schema	`0.1.6`	indirect
npm	@jridgewell/gen-mapping	`0.3.13`	indirect
npm	@jridgewell/resolve-uri	`3.1.0`	indirect
npm	@jridgewell/source-map	`0.3.11`	indirect
npm	@jridgewell/sourcemap-codec	`1.5.5`	indirect
npm	@jridgewell/trace-mapping	`0.3.31`	indirect
npm	@playwright/test	`1.62.0`	indirect
npm	@rollup/plugin-terser	`1.0.0`	indirect
npm	@rollup/rollup-android-arm-eabi	`4.62.2`	indirect
npm	@rollup/rollup-android-arm64	`4.62.2`	indirect
npm	@rollup/rollup-darwin-arm64	`4.62.2`	indirect
npm	@rollup/rollup-darwin-x64	`4.62.2`	indirect
npm	@rollup/rollup-freebsd-arm64	`4.62.2`	indirect
npm	@rollup/rollup-freebsd-x64	`4.62.2`	indirect
npm	@rollup/rollup-linux-arm-gnueabihf	`4.62.2`	indirect
npm	@rollup/rollup-linux-arm-musleabihf	`4.62.2`	indirect
npm	@rollup/rollup-linux-arm64-gnu	`4.62.2`	indirect
npm	@rollup/rollup-linux-arm64-musl	`4.62.2`	indirect
npm	@rollup/rollup-linux-loong64-gnu	`4.62.2`	indirect
npm	@rollup/rollup-linux-loong64-musl	`4.62.2`	indirect
npm	@rollup/rollup-linux-ppc64-gnu	`4.62.2`	indirect
npm	@rollup/rollup-linux-ppc64-musl	`4.62.2`	indirect
npm	@rollup/rollup-linux-riscv64-gnu	`4.62.2`	indirect
npm	@rollup/rollup-linux-riscv64-musl	`4.62.2`	indirect
npm	@rollup/rollup-linux-s390x-gnu	`4.62.2`	indirect
npm	@rollup/rollup-linux-x64-gnu	`4.62.2`	indirect
npm	@rollup/rollup-linux-x64-musl	`4.62.2`	indirect
npm	@rollup/rollup-openbsd-x64	`4.62.2`	indirect
npm	@rollup/rollup-openharmony-arm64	`4.62.2`	indirect
npm	@rollup/rollup-win32-arm64-msvc	`4.62.2`	indirect
npm	@rollup/rollup-win32-ia32-msvc	`4.62.2`	indirect
npm	@rollup/rollup-win32-x64-gnu	`4.62.2`	indirect
npm	@rollup/rollup-win32-x64-msvc	`4.62.2`	indirect
npm	@types/estree	`1.0.9`	indirect
npm	@types/istanbul-lib-coverage	`2.0.6`	indirect
npm	acorn	`8.17.0`	indirect
npm	ansi-colors	`4.1.3`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	anymatch	`3.1.3`	indirect
npm	argparse	`2.0.1`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	binary-extensions	`2.3.0`	indirect
npm	brace-expansion	`1.1.16`	indirect
npm	brace-expansion	`2.0.1`	indirect
npm	braces	`3.0.3`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	buffer-from	`1.1.2`	indirect
npm	c8	`8.0.1`	indirect
npm	camelcase	`6.3.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	chokidar	`3.6.0`	indirect
npm	cliui	`7.0.4`	indirect
npm	cliui	`8.0.1`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	commander	`2.20.3`	indirect
npm	concat-map	`0.0.1`	indirect
npm	convert-source-map	`2.0.0`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	debug	`4.4.1`	indirect
npm	decamelize	`4.0.0`	indirect
npm	diff	`5.2.0`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	escalade	`3.1.1`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	fill-range	`7.1.1`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat	`5.0.2`	indirect
npm	foreground-child	`2.0.0`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	fsevents	`2.3.2`	indirect
npm	fsevents	`2.3.3`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	glob	`7.2.3`	indirect
npm	glob	`8.1.0`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	has-flag	`4.0.0`	indirect
npm	he	`1.2.0`	indirect
npm	html-escaper	`2.0.2`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	indirect
npm	is-binary-path	`2.1.0`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-number	`7.0.0`	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.0`	indirect
npm	istanbul-lib-report	`3.0.1`	indirect
npm	istanbul-reports	`3.2.0`	indirect
npm	js-yaml	`4.3.0`	indirect
npm	locate-path	`6.0.0`	indirect
npm	log-symbols	`4.1.0`	indirect
npm	make-dir	`4.0.0`	indirect
npm	minimatch	`3.1.5`	indirect
npm	minimatch	`5.1.6`	indirect
npm	mocha	`10.8.2`	indirect
npm	ms	`2.1.3`	indirect
npm	normalize-path	`3.0.0`	indirect
npm	once	`1.4.0`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-is-absolute	`1.0.1`	indirect
npm	path-key	`3.1.1`	indirect
npm	picomatch	`2.3.1`	indirect
npm	playwright	`1.62.0`	indirect
npm	playwright-core	`1.62.0`	indirect
npm	randombytes	`2.1.0`	indirect
npm	readdirp	`3.6.0`	indirect
npm	require-directory	`2.1.1`	indirect
npm	rimraf	`3.0.2`	indirect
npm	rollup	`4.62.2`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	semver	`7.8.5`	indirect
npm	serialize-javascript	`6.0.2`	indirect
npm	serialize-javascript	`7.0.7`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	signal-exit	`3.0.7`	indirect
npm	smob	`1.6.2`	indirect
npm	source-map	`0.6.1`	indirect
npm	source-map-support	`0.5.21`	indirect
npm	string-width	`4.2.3`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-color	`8.1.1`	indirect
npm	terser	`5.49.0`	indirect
npm	test-exclude	`6.0.0`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	v8-to-istanbul	`9.3.0`	indirect
npm	which	`2.0.2`	indirect
npm	workerpool	`6.5.1`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yargs	`16.2.0`	indirect
npm	yargs	`17.7.3`	indirect
npm	yargs-parser	`20.2.9`	indirect
npm	yargs-parser	`21.1.1`	indirect
npm	yargs-unparser	`2.0.0`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 7

This repository publishes no package the index resolves, so its own dependency graph was assessed — 147 packages, which also include development and test pins that never ship: 7 carry known advisories, of which 0 are direct.

Package	Version	Relation	Severity	Advisories	Fixed in
brace-expansion	`1.1.16`	indirect	high	2	`5.0.9`
brace-expansion	`2.0.1`	indirect	high	5	`5.0.9`
js-yaml	`4.3.0`	indirect	high	1	`4.3.1`
minimatch	`5.1.6`	indirect	high	3	`10.2.3`
picomatch	`2.3.1`	indirect	high	2	`4.0.4`
serialize-javascript	`6.0.2`	indirect	high	2	`7.0.5`
diff	`5.2.0`	indirect	moderate	1	`8.0.3`

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