Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 22:03 UTC

metarhia / Example

Metarhia application example for Node.js 🟢

JavaScriptMIT★ 211 stars⑂ 82 forkssince Apr 2020View on GitHub ↗

#nodejs #node #starter-kit #server #api #project #isolation #threads #cloud #cluster #sandboxing #metarhia #metaserverless

metarhia/Example holds a health index of 59 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (74/100) and lowest on Vitality (45/100). It was last updated 38 days ago. A single contributor accounts for most of its recent work.

overall / 100

Moderate

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

Ownership

MetarhiaOrganization · verified domain

748 followers98 public repossince Mar 2016

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	metarhiapoints to another repo — not scored	0.0.1	20	1	3663 days ago	metarhia cloud jstp impress console globalstorage

Metrics by category

Vitality

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

45Weak · 21% of overall

Development activity

34At Risk

How it's scored

18/36	Push recency — last push 38 days ago
4.8/36	Commit cadence — 7/52 weeks with commits
10.6/18	Commit volume — 14 commits in the last year
1/10	OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1

Inputs used

commits_last_year	14
human_commit_share	1
days_since_last_push	38
active_weeks_last_year	7

Release discipline

62Moderate

How it's scored

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

Inputs used

releases_count	10
latest_release_tag	v3.1.0
releases_from_tags	no
days_since_latest_release	358
mean_days_between_releases	202.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?

55Moderate · 17% of overall

Popularity & adoption

60Moderate

How it's scored

37.7/60	Stars — 211 stars
15.9/25	Forks — 82 forks
6.8/15	Watchers — 18 watchers

Inputs used

forks	82
stars	211
watchers	18
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

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

57Moderate · 23% of overall

Maintainer resilience (bus factor)

34At Risk

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
1.5/22.5	Commit distribution — top contributor authored 93% of commits
13.5/13.5	Contributor breadth — 13 contributors
10/10	OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations

Inputs used

bus_factor	1
contributors_sampled	13
top_contributor_share	0.933

Issue & PR responsiveness

45Weak

How it's scored

27.4/42	Issue resolution — 65% of issues closed
7.1/30	PR acceptance — 54/227 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15	OpenSSF Scorecard: Code-Review — Found 4/12 approved changesets -- score normalized to 3

Inputs used

merged_prs	54
open_issues	17
closed_issues	32
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.653
closed_unmerged_prs	173
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

96Exceptional

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
20.7/25	Owner reach — 748 followers of metarhia
25/25	Track record — 98 public repos, account ~10 yr old

Inputs used

followers	748
owner_type	Organization
is_verified	yes
owner_login	metarhia
public_repos	98
account_age_days	3,824

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall

Engineering practices

80Excellent

How it's scored

24/24	CI workflows — 1 workflow(s)
24/24	Tests present
16/16	Linter config — eslint.config.js
0/9.6	Pre-commit hooks
6.4/6.4	.editorconfig
10/20	OpenSSF Scorecard: CI-Tests — 7 out of 12 merged PRs checked by a CI test -- score normalized to 5

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	yes
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://metarhia.com
10/10	Repository description
10/10	Topics — 13 topics
0/10	Wiki

Inputs used

topics	nodejs, node, starter-kit, server, api, project, isolation, threads, cloud, cluster, sandboxing, metarhia, metaserverless
has_wiki	no
homepage	https://metarhia.com
docs_site	https://metarhia.com
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?

52Moderate · 16% of overall

Security posture

40Weak

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
1.2/2.5	CI-Tests — 7 out of 12 merged PRs checked by a CI test -- score normalized to 5
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5	Code-Review — Found 4/12 approved changesets -- score normalized to 3
2.5/2.5	Contributors — project has 8 contributing companies or organizations
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
0.8/7.5	Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
0/5	Packaging — no data
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
6/7.5	Vulnerabilities — 2 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	15
scorecard_version	v5.5.0
checks_inconclusive	3
scorecard_aggregate	4

Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, 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	2
affected_packages	2
assessed_packages	132
unassessed_packages	0
affected_by_severity	high 1, 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 132 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.

51Moderate · 4% of overall

Agent context & guidance

3Critical

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
3.2/40	Legible commit history — 6 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.06
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

56Moderate

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
11/11	Lint / format config — eslint.config.js
11/11	Static type checking — 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
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	tsconfig.json
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0

Code legibility for models

82Excellent

How it's scored

27/45	Type-checkable code — JavaScript with type-check config (tsconfig.json)
55/55	Manageable file sizes — 0/99 source files over 60KB

Inputs used

primary_language	JavaScript
largest_source_bytes	13,860
source_files_sampled	99
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 — example

Inputs used

example_dirs	example
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

211GitHub stars

13contributors

14commits, last 12 months

38days since last push

10releases

1bus factor

17open issues

npmpackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
npm package 'metarhia' points at a different repository (https://github.com/metarhia/Metarhia); excluded from ecosystem scoring

More detail

Star and fork history 0 ★ / 82 ⇿

0Stars

82Forks

10Releases

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 3Patch 5

Each point covers 6 days.

OpenSSF Scorecard 4.0 / 10

4.0aggregate

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-13 22:03 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
5	CI-Tests	7 out of 12 merged PRs checked by a CI test -- score normalized to 5
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
3	Code-Review	Found 4/12 approved changesets -- score normalized to 3
10	Contributors	project has 8 contributing companies or organizations
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
1	Maintained	2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
n/a	Packaging	packaging workflow not 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
8	Vulnerabilities	2 existing vulnerabilities detected

Direct dependencies 4

Registry	Package	Version constraint	Manifest
npm	impress	`^3.1.2`	package.json
npm	metasql	`^3.0.0-alpha.4`	package.json
npm	pg	`^8.22.0`	package.json
npm	redis	`^5.12.1`	package.json

All dependencies 132

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

Registry	Package	Version	Relation
npm	impress	`3.1.2`	direct
npm	metasql	`3.0.0-alpha.4`	direct
npm	pg	`8.22.0`	direct
npm	redis	`5.12.1`	direct
npm	@eslint-community/eslint-utils	`4.9.0`	indirect
npm	@eslint-community/regexpp	`4.12.2`	indirect
npm	@eslint/config-array	`0.21.2`	indirect
npm	@eslint/config-helpers	`0.4.2`	indirect
npm	@eslint/core	`0.17.0`	indirect
npm	@eslint/eslintrc	`3.3.6`	indirect
npm	@eslint/js	`9.39.5`	indirect
npm	@eslint/object-schema	`2.1.7`	indirect
npm	@eslint/plugin-kit	`0.4.1`	indirect
npm	@humanfs/core	`0.19.1`	indirect
npm	@humanfs/node	`0.16.7`	indirect
npm	@humanwhocodes/module-importer	`1.0.1`	indirect
npm	@humanwhocodes/retry	`0.4.3`	indirect
npm	@pkgr/core	`0.2.9`	indirect
npm	@redis/bloom	`5.12.1`	indirect
npm	@redis/client	`5.12.1`	indirect
npm	@redis/json	`5.12.1`	indirect
npm	@redis/search	`5.12.1`	indirect
npm	@redis/time-series	`5.12.1`	indirect
npm	@types/estree	`1.0.8`	indirect
npm	@types/json-schema	`7.0.15`	indirect
npm	@types/node	`24.13.3`	indirect
npm	@types/pg	`8.20.4`	indirect
npm	@types/ws	`8.18.1`	indirect
npm	acorn	`8.18.0`	indirect
npm	acorn-jsx	`5.3.2`	indirect
npm	ajv	`6.15.0`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	argparse	`2.0.1`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	brace-expansion	`1.1.18`	indirect
npm	callsites	`3.1.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	cluster-key-slot	`1.1.2`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	concat-map	`0.0.1`	indirect
npm	concolor	`1.1.3`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	debug	`4.4.3`	indirect
npm	deep-is	`0.1.4`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	eslint	`9.39.5`	indirect
npm	eslint-config-metarhia	`9.1.9`	indirect
npm	eslint-config-prettier	`10.1.8`	indirect
npm	eslint-plugin-prettier	`5.5.5`	indirect
npm	eslint-scope	`8.4.0`	indirect
npm	eslint-visitor-keys	`3.4.3`	indirect
npm	eslint-visitor-keys	`4.2.1`	indirect
npm	espree	`10.4.0`	indirect
npm	esquery	`1.6.0`	indirect
npm	esrecurse	`4.3.0`	indirect
npm	estraverse	`5.3.0`	indirect
npm	esutils	`2.0.3`	indirect
npm	fast-deep-equal	`3.1.3`	indirect
npm	fast-diff	`1.3.0`	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	find-up	`5.0.0`	indirect
npm	flat-cache	`4.0.1`	indirect
npm	flatted	`3.4.4`	indirect
npm	glob-parent	`6.0.2`	indirect
npm	globals	`14.0.0`	indirect
npm	has-flag	`4.0.0`	indirect
npm	ignore	`5.3.2`	indirect
npm	import-fresh	`3.3.1`	indirect
npm	imurmurhash	`0.1.4`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-glob	`4.0.3`	indirect
npm	isexe	`2.0.0`	indirect
npm	js-yaml	`4.3.1`	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	keyv	`4.5.4`	indirect
npm	levn	`0.4.1`	indirect
npm	locate-path	`6.0.0`	indirect
npm	lodash.merge	`4.6.2`	indirect
npm	metacom	`3.2.6`	indirect
npm	metaconfiguration	`3.0.3`	indirect
npm	metadomain	`2.0.0-alpha.3`	indirect
npm	metalog	`3.1.18`	indirect
npm	metaschema	`2.2.2`	indirect
npm	metautil	`5.4.0`	indirect
npm	metavm	`1.4.5`	indirect
npm	metawatch	`1.2.4`	indirect
npm	minimatch	`3.1.5`	indirect
npm	ms	`2.1.3`	indirect
npm	natural-compare	`1.4.0`	indirect
npm	optionator	`0.9.4`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	parent-module	`1.0.1`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	pg-cloudflare	`1.4.0`	indirect
npm	pg-connection-string	`2.14.0`	indirect
npm	pg-int8	`1.0.1`	indirect
npm	pg-pool	`3.14.0`	indirect
npm	pg-protocol	`1.15.0`	indirect
npm	pg-types	`2.2.0`	indirect
npm	pgpass	`1.0.5`	indirect
npm	postgres-array	`2.0.0`	indirect
npm	postgres-bytea	`1.0.0`	indirect
npm	postgres-date	`1.0.7`	indirect
npm	postgres-interval	`1.2.0`	indirect
npm	prelude-ls	`1.2.1`	indirect
npm	prettier	`3.8.2`	indirect
npm	prettier	`3.9.6`	indirect
npm	prettier-linter-helpers	`1.0.1`	indirect
npm	punycode	`2.3.1`	indirect
npm	resolve-from	`4.0.0`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	split2	`4.2.0`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	supports-color	`7.2.0`	indirect
npm	synckit	`0.11.12`	indirect
npm	type-check	`0.4.0`	indirect
npm	typescript	`5.9.3`	indirect
npm	undici-types	`7.18.2`	indirect
npm	uri-js	`4.4.1`	indirect
npm	which	`2.0.2`	indirect
npm	word-wrap	`1.2.5`	indirect
npm	ws	`8.21.2`	indirect
npm	xtend	`4.0.2`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 2

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

Package	Version	Relation	Severity	Advisories	Fixed in
js-yaml	`4.3.1`	indirect	high	1	`4.3.2`
@humanfs/node	`0.16.7`	indirect	moderate	1	`0.16.8`

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