Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-04 08:44 UTC

monyone / aribb24.js

an alternative implementation for b24.js

TypeScriptMIT★ 57 stars⑂ 4 forkssince Jan 2021View on GitHub ↗

KindLibraryCommand-line toolhow this is determined

monyone/aribb24.js holds a health index of 41 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (53/100) and lowest on Vitality (30/100). It was last updated 36 days ago. A single contributor accounts for most of its recent work.

41

overall / 100

Weak

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.

41

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

Ownership

もにょ～んPersonal account

31 followers49 public repossince Mar 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	aribb24.js	2.0.25	2,825	197	36 days ago	html5 arib b24 subtitle

Metrics by category

Vitality

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

30At Risk · 21% of overall

Development activity

49Weak

How it's scored

18/36	Push recency — last push 36 days ago
6.2/36	Commit cadence — 9/52 weeks with commits
14.6/18	Commit volume — 41 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	41
human_commit_share	1
days_since_last_push	36
active_weeks_last_year	9

Release discipline

1Critical

How it's scored

0/27	Ships releases — no releases published
0/36	Release recency — no releases
0/27	Release cadence — no releases
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count

0

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?

46Weak · 17% of overall

Popularity & adoption

35Weak

How it's scored

28.4/60	Stars — 57 stars
4/25	Forks — 4 forks
2.7/15	Watchers — 4 watchers

Inputs used

forks	4
stars	57
watchers	4
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	shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

58Moderate

How it's scored

46/80	Monthly downloads — 2,825 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	aribb24.js
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	2,825
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?

53Moderate · 23% of overall

Maintainer resilience (bus factor)

18Critical

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	4
top_contributor_share	0.975

Issue & PR responsiveness

54Moderate

How it's scored

0/42	Issue resolution — no issues or no data
24.5/30	PR acceptance — 9/11 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/30 approved changesets -- score normalized to 0

Inputs used

merged_prs	9
open_issues	0
closed_issues	0
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	—
closed_unmerged_prs	2
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): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

56Moderate

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
10.8/25	Owner reach — 31 followers of monyone
24.4/25	Track record — 49 public repos, account ~13 yr old

Inputs used

followers	31
owner_type	User
is_verified	—
owner_login	monyone
public_repos	49
account_age_days	4,924

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

Inputs used

packages	aribb24.js
ecosystems	npm
any_deprecated	no
min_days_since_publish	36

Engineering Quality

Are baseline engineering and documentation practices in place?

47Weak · 19% of overall

Engineering practices

38Weak

How it's scored

0/24	CI workflows
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
6.4/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — no data

Inputs used

has_ci	no
has_tests	yes
has_editorconfig	yes
has_linter_config	no
has_precommit_config	no

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

60Moderate

How it's scored

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

Inputs used

topics	aribb24
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?

42Weak · 16% of overall

Security posture

27At Risk

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 — no data
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/30 approved changesets -- score normalized to 0
0.8/2.5	Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10	Dangerous-Workflow — no data
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 — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
0/5	SAST — no SAST tool detected
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — no data
0/7.5	Vulnerabilities — 17 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	12
scorecard_version	v5.5.0
checks_inconclusive	6
scorecard_aggregate	2.7

Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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	17
affected_packages	6
assessed_packages	112
unassessed_packages	0
affected_by_severity	critical 1, high 5
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 112 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.

49Weak · 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)
25.6/40	Legible commit history — 48 of 100 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.48
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

48Weak

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
11/11	Static type checking — src/runtime/cli/tsconfig.json, test/tsconfig.json, tsconfig.json
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	yes
lockfiles	yarn.lock
has_dockerfile	no
typed_language	yes
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	src/runtime/cli/tsconfig.json, test/tsconfig.json, tsconfig.json
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

100Exceptional

How it's scored

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

Inputs used

primary_language	TypeScript
largest_source_bytes	454,356
source_files_sampled	130
oversized_source_files	1

Key facts

57GitHub stars

4contributors

41commits, last 12 months

36days since last push

0releases

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 ★ / 4 ⇿

0Stars

4Forks

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 2.7 / 10

2.7aggregate

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-04 08:43 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
n/a	CI-Tests	no pull request found
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 0/30 approved changesets -- score normalized to 0
3	Contributors	project has 1 contributing companies or organizations -- score normalized to 3
n/a	Dangerous-Workflow	no workflows found
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
10	Maintained	13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
0	SAST	no SAST tool detected
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
n/a	Token-Permissions	No tokens found
0	Vulnerabilities	17 existing vulnerabilities detected

All dependencies 112

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

Registry	Package	Version	Relation
npm	@blazediff/core	`1.9.1`	indirect
npm	@emnapi/core	`1.9.2`	indirect
npm	@emnapi/runtime	`1.9.2`	indirect
npm	@emnapi/wasi-threads	`1.2.1`	indirect
npm	@jridgewell/sourcemap-codec	`1.5.5`	indirect
npm	@napi-rs/canvas	`0.1.98`	indirect
npm	@napi-rs/canvas-android-arm64	`0.1.98`	indirect
npm	@napi-rs/canvas-darwin-arm64	`0.1.98`	indirect
npm	@napi-rs/canvas-darwin-x64	`0.1.98`	indirect
npm	@napi-rs/canvas-linux-arm-gnueabihf	`0.1.98`	indirect
npm	@napi-rs/canvas-linux-arm64-gnu	`0.1.98`	indirect
npm	@napi-rs/canvas-linux-arm64-musl	`0.1.98`	indirect
npm	@napi-rs/canvas-linux-riscv64-gnu	`0.1.98`	indirect
npm	@napi-rs/canvas-linux-x64-gnu	`0.1.98`	indirect
npm	@napi-rs/canvas-linux-x64-musl	`0.1.98`	indirect
npm	@napi-rs/canvas-win32-arm64-msvc	`0.1.98`	indirect
npm	@napi-rs/canvas-win32-x64-msvc	`0.1.98`	indirect
npm	@napi-rs/wasm-runtime	`1.1.4`	indirect
npm	@oxc-project/types	`0.124.0`	indirect
npm	@polka/url	`1.0.0-next.28`	indirect
npm	@rolldown/binding-android-arm64	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-darwin-arm64	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-darwin-x64	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-freebsd-x64	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-linux-arm-gnueabihf	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-linux-arm64-gnu	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-linux-arm64-musl	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-linux-ppc64-gnu	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-linux-s390x-gnu	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-linux-x64-gnu	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-linux-x64-musl	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-openharmony-arm64	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-wasm32-wasi	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-win32-arm64-msvc	`1.0.0-rc.15`	indirect
npm	@rolldown/binding-win32-x64-msvc	`1.0.0-rc.15`	indirect
npm	@rolldown/pluginutils	`1.0.0-rc.15`	indirect
npm	@standard-schema/spec	`1.1.0`	indirect
npm	@tybys/wasm-util	`0.10.1`	indirect
npm	@types/chai	`5.2.3`	indirect
npm	@types/deep-eql	`4.0.2`	indirect
npm	@types/estree	`1.0.6`	indirect
npm	@types/node	`24.12.2`	indirect
npm	@vitest/browser	`4.1.4`	indirect
npm	@vitest/browser-playwright	`4.1.4`	indirect
npm	@vitest/expect	`4.1.4`	indirect
npm	@vitest/mocker	`4.1.4`	indirect
npm	@vitest/pretty-format	`4.1.4`	indirect
npm	@vitest/runner	`4.1.4`	indirect
npm	@vitest/snapshot	`4.1.4`	indirect
npm	@vitest/spy	`4.1.4`	indirect
npm	@vitest/utils	`4.1.4`	indirect
npm	assertion-error	`2.0.1`	indirect
npm	balanced-match	`4.0.4`	indirect
npm	brace-expansion	`5.0.5`	indirect
npm	chai	`6.2.2`	indirect
npm	convert-source-map	`2.0.0`	indirect
npm	detect-libc	`2.1.2`	indirect
npm	es-module-lexer	`2.0.0`	indirect
npm	estree-walker	`3.0.3`	indirect
npm	expect-type	`1.3.0`	indirect
npm	fdir	`6.5.0`	indirect
npm	fsevents	`2.3.2`	indirect
npm	fsevents	`2.3.3`	indirect
npm	glob	`13.0.6`	indirect
npm	lightningcss	`1.32.0`	indirect
npm	lightningcss-android-arm64	`1.32.0`	indirect
npm	lightningcss-darwin-arm64	`1.32.0`	indirect
npm	lightningcss-darwin-x64	`1.32.0`	indirect
npm	lightningcss-freebsd-x64	`1.32.0`	indirect
npm	lightningcss-linux-arm-gnueabihf	`1.32.0`	indirect
npm	lightningcss-linux-arm64-gnu	`1.32.0`	indirect
npm	lightningcss-linux-arm64-musl	`1.32.0`	indirect
npm	lightningcss-linux-x64-gnu	`1.32.0`	indirect
npm	lightningcss-linux-x64-musl	`1.32.0`	indirect
npm	lightningcss-win32-arm64-msvc	`1.32.0`	indirect
npm	lightningcss-win32-x64-msvc	`1.32.0`	indirect
npm	lru-cache	`11.0.1`	indirect
npm	magic-string	`0.30.21`	indirect
npm	minimatch	`10.2.5`	indirect
npm	minipass	`7.1.2`	indirect
npm	minipass	`7.1.3`	indirect
npm	mrmime	`2.0.0`	indirect
npm	nanoid	`3.3.11`	indirect
npm	obug	`2.1.1`	indirect
npm	package-json-from-dist	`1.0.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.4`	indirect
npm	playwright	`1.59.1`	indirect
npm	playwright-core	`1.59.1`	indirect
npm	pngjs	`7.0.0`	indirect
npm	postcss	`8.5.10`	indirect
npm	rimraf	`6.1.3`	indirect
npm	rolldown	`1.0.0-rc.15`	indirect
npm	siginfo	`2.0.0`	indirect
npm	sirv	`3.0.2`	indirect
npm	source-map-js	`1.2.1`	indirect
npm	stackback	`0.0.2`	indirect
npm	std-env	`4.1.0`	indirect
npm	tinybench	`2.9.0`	indirect
npm	tinyexec	`1.1.1`	indirect
npm	tinyglobby	`0.2.16`	indirect
npm	tinyrainbow	`3.1.0`	indirect
npm	totalist	`3.0.1`	indirect
npm	tslib	`2.8.1`	indirect
npm	typescript	`6.0.3`	indirect
npm	undici-types	`7.16.0`	indirect
npm	vite	`8.0.8`	indirect
npm	vitest	`4.1.4`	indirect
npm	why-is-node-running	`2.3.0`	indirect
npm	ws	`8.20.0`	indirect

Dependency advisories 6

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

Package	Version	Relation	Severity	Advisories	Fixed in
@vitest/browser	`4.1.4`	indirect	critical	3	`5.0.0-beta.6`
brace-expansion	`5.0.5`	indirect	high	4	`5.0.9`
nanoid	`3.3.11`	indirect	high	3	`5.1.16`
postcss	`8.5.10`	indirect	high	3	`8.5.23`
vite	`8.0.8`	indirect	high	2	`8.0.16`
ws	`8.20.0`	indirect	high	2	`8.21.0`

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.