Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-07-26 15:55 UTC

metarhia / metacom

RPC communication protocol for Metarhia stack 🔌

JavaScriptMIT★ 81 stars⑂ 48 forkssince Apr 2018View on GitHub ↗

metarhia/metacom holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Engineering Quality (80/100) and lowest on AI Readiness (46/100). It was last updated 20 days ago. A single contributor accounts for most of its recent work.

78
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.

78
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)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

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

Ownership

MetarhiaOrganization
742 followers97 public repossince Mar 2016

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmmetacom3.2.692472309 days agometacommetarhiaimpressserverclientsocketwebsocketrpceventssyncglobalstorageprotocolstream

Metrics by category

Vitality

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

69Good · 21% of overall
How it's scored
28.8/36Push recencylast push 20 days ago
11.8/36Commit cadence17/52 weeks with commits
18/18Commit volume106 commits in the last year
10/10OpenSSF Scorecard: Maintained28 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year106
human_commit_share0.99
days_since_last_push20
active_weeks_last_year17
How it's scored
27/27Ships releases60 releases published
16.2/36Release recencylatest release 309 days ago
19.8/27Release cadencea release every ~82 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count60
latest_release_tagv3.2.6
releases_from_tagsno
days_since_latest_release309
mean_days_between_releases82
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?

60Moderate · 17% of overall
How it's scored
30.9/60Stars81 stars
13.9/25Forks48 forks
7.1/15Watchers20 watchers
Inputs used
forks48
stars81
watchers20
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
39.5/80Monthly downloads924 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesmetacom
dependents
ecosystemsnpm
total_downloads
monthly_downloads924
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?

66Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2.9/22.5Commit distributiontop contributor authored 87% of commits
13.5/13.5Contributor breadth21 contributors
10/10OpenSSF Scorecard: Contributorsproject has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled21
top_contributor_share0.87
How it's scored
41/42Issue resolution98% of issues closed
5.7/30PR acceptance75/398 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/29 approved changesets -- score normalized to 0
Inputs used
merged_prs75
open_issues3
closed_issues129
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.977
closed_unmerged_prs323
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
20.6/25Owner reach742 followers of metarhia
25/25Track record97 public repos, account ~10 yr old
Inputs used
followers742
owner_typeOrganization
is_verified
owner_loginmetarhia
public_repos97
account_age_days3,775
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
26/35Publish recencylatest publish 309 days ago
20/20Version history72 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesmetacom
ecosystemsnpm
any_deprecatedno
min_days_since_publish309

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configeslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests3 out of 3 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://metarhia.com
10/10Repository description
10/10Topics20 topics
0/10Wiki
Inputs used
topicsmetarhia, impress, rpc, tcp, ws, nodejs, node, ipc, client, server, api, highload, websocket, json, stream, protocol, hacktoberfest, meta-edu, rest, wss
has_wikino
homepagehttps://metarhia.com
docs_sitehttps://metarhia.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

65Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests3 out of 3 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/29 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 9 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained28 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
5.2/7.5Vulnerabilities3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages2
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:metacom@3.2.6 runtime dependency closure — what installing the published package pulls in — 2 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
3.8/40Legible commit history7 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.071
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configeslint.config.js
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance1 of the last 100 commits are automated dependency updates
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.01
How it's scored
27/45Type-checkable codeJavaScript with type-check config (tsconfig.json)
55/55Manageable file sizes0/35 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes21,603
source_files_sampled35
oversized_source_files0

Key facts

81GitHub stars
21contributors
106commits, last 12 months
20days since last push
60releases
1bus factor
3open 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 ★ / 48 ⇿
0Stars
48Forks
60Releases

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.

010203040504832018-042022-032026-02
Major 4Minor 10Patch 33

Each point covers 8 days.

OpenSSF Scorecard 5.6 / 10
5.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-07-26 15:54 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests3 out of 3 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/29 approved changesets -- score normalized to 0
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained28 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmmetautil^5.4.0package.json
All dependencies 99

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

RegistryPackageVersionRelation
npmmetautil5.5.2direct
npm@eslint-community/eslint-utils4.9.1indirect
npm@eslint-community/regexpp4.12.2indirect
npm@eslint/config-array0.21.2indirect
npm@eslint/config-helpers0.4.2indirect
npm@eslint/core0.17.0indirect
npm@eslint/eslintrc3.3.5indirect
npm@eslint/js9.39.4indirect
npm@eslint/object-schema2.1.7indirect
npm@eslint/plugin-kit0.4.1indirect
npm@humanfs/core0.19.1indirect
npm@humanfs/node0.16.7indirect
npm@humanwhocodes/module-importer1.0.1indirect
npm@humanwhocodes/retry0.4.3indirect
npm@pkgr/core0.2.9indirect
npm@types/estree1.0.8indirect
npm@types/json-schema7.0.15indirect
npm@types/node25.9.3indirect
npmacorn8.16.0indirect
npmacorn-jsx5.3.2indirect
npmajv6.14.0indirect
npmansi-styles4.3.0indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.15indirect
npmcallsites3.1.0indirect
npmchalk4.1.2indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdeep-is0.1.4indirect
npmescape-string-regexp4.0.0indirect
npmeslint9.39.4indirect
npmeslint-config-metarhia9.1.9indirect
npmeslint-config-prettier10.1.8indirect
npmeslint-plugin-prettier5.5.5indirect
npmeslint-scope8.4.0indirect
npmeslint-visitor-keys3.4.3indirect
npmeslint-visitor-keys4.2.1indirect
npmespree10.4.0indirect
npmesquery1.7.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmfast-deep-equal3.1.3indirect
npmfast-diff1.3.0indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfile-entry-cache8.0.0indirect
npmfind-up5.0.0indirect
npmflat-cache4.0.1indirect
npmflatted3.4.2indirect
npmglob-parent6.0.2indirect
npmglobals14.0.0indirect
npmhas-flag4.0.0indirect
npmignore5.3.2indirect
npmimport-fresh3.3.1indirect
npmimurmurhash0.1.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmisexe2.0.0indirect
npmjs-yaml4.2.0indirect
npmjson-buffer3.0.1indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmkeyv4.5.4indirect
npmlevn0.4.1indirect
npmlocate-path6.0.0indirect
npmlodash.merge4.6.2indirect
npmmetarhia-build0.0.3indirect
npmminimatch3.1.5indirect
npmms2.1.3indirect
npmnatural-compare1.4.0indirect
npmoptionator0.9.4indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmparent-module1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-key3.1.1indirect
npmprelude-ls1.2.1indirect
npmprettier3.8.2indirect
npmprettier3.8.4indirect
npmprettier-linter-helpers1.0.1indirect
npmpunycode2.3.1indirect
npmresolve-from4.0.0indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmsynckit0.11.12indirect
npmtype-check0.4.0indirect
npmtypescript5.9.3indirect
npmundici-types7.24.6indirect
npmuri-js4.4.1indirect
npmwhich2.0.2indirect
npmword-wrap1.2.5indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:metacom@3.2.6 pulls in 2 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.

The message is kept through sign-in.

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.27.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.