Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 18:27 UTC

metarhia / do

Simplest way to manage asynchronicity

JavaScriptMIT★ 45 stars⑂ 6 forkssince Jan 2013View on GitHub ↗

#node #nodejs #js #javascript #metarhia #async #asynchronous #callback #highload #parallel #series #composition #promise #await #collector #synchronous #impress #thenable #chain #promisify

metarhia/do holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Engineering Quality (73/100) and lowest on AI Readiness (37/100). It was last updated 5 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 62 is calibrated to 69 on the published index scale (record calibration 2026-08-02).

Ownership

MetarhiaOrganization · verified domain

750 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	do	0.7.1	1,917	37	33 days ago	metasync callback callbacks promise sync async chain asyncronous parallel sequential metarhia step control flow collector errback err-first error-first callback-last datacollector keycollector composition

Metrics by category

Vitality

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

60Moderate · 21% of overall

Development activity

49Weak

How it's scored

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

Inputs used

commits_last_year	6
human_commit_share	0.98
days_since_last_push	5
active_weeks_last_year	1

Release discipline

76Good

How it's scored

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

Inputs used

releases_count	2
latest_release_tag	v0.7.1
releases_from_tags	no
days_since_latest_release	33
mean_days_between_releases	1,905.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?

56Moderate · 17% of overall

Popularity & adoption

39Weak

How it's scored

26.7/60	Stars — 45 stars
5.8/25	Forks — 6 forks
6.2/15	Watchers — 14 watchers

Inputs used

forks	6
stars	45
watchers	14
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

77Good

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
18/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
6.3/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	4
has_contributing	yes
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	badge.fury.io, github.com, shields.io
has_pull_request_template	yes

Ecosystem adoption (downloads)

55Moderate

How it's scored

43.8/80	Monthly downloads — 1,917 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	do
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	1,917
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?

62Moderate · 23% of overall

Maintainer resilience (bus factor)

35Weak

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	6
top_contributor_share	0.64

Issue & PR responsiveness

28At Risk

How it's scored

22.2/42	Issue resolution — 53% of issues closed
2.5/30	PR acceptance — 6/73 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 1/20 approved changesets -- score normalized to 0

Inputs used

merged_prs	6
open_issues	8
closed_issues	9
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.529
closed_unmerged_prs	67
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 — 750 followers of metarhia
25/25	Track record — 98 public repos, account ~10 yr old

Inputs used

followers	750
owner_type	Organization
is_verified	yes
owner_login	metarhia
public_repos	98
account_age_days	3,829

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	do
ecosystems	npm
any_deprecated	no
min_days_since_publish	33

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall

Engineering practices

78Good

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
8/20	OpenSSF Scorecard: CI-Tests — 2 out of 5 merged PRs checked by a CI test -- score normalized to 4

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 — 20 topics
0/10	Wiki

Inputs used

topics	node, nodejs, js, javascript, metarhia, async, asynchronous, callback, highload, parallel, series, composition, promise, await, collector, synchronous, impress, thenable, chain, promisify
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?

65Good · 16% of overall

Security posture

56Moderate

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.5	CI-Tests — 2 out of 5 merged PRs checked by a CI test -- score normalized to 4
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 1/20 approved changesets -- score normalized to 0
2.5/2.5	Contributors — project has 10 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
3.8/7.5	Maintained — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
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
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
6.8/7.5	Vulnerabilities — 1 existing vulnerabilities detected

Inputs used

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

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	1
affected_packages	1
assessed_packages	129
unassessed_packages	0
affected_by_severity	high 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 129 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.

37Weak · 4% of overall

Agent context & guidance

6Critical

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.112
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

53Moderate

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
11/11	Lint / format config — eslint.config.js
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 — 2 of the last 100 commits are automated dependency updates
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	—
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0.02

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	7,512
source_files_sampled	5
oversized_source_files	0

Key facts

45GitHub stars

6contributors

6commits, last 12 months

5days since last push

2releases

1bus factor

8open 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

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

Each point covers 10 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-09-18 18:26 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
4	CI-Tests	2 out of 5 merged PRs checked by a CI test -- score normalized to 4
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 1/20 approved changesets -- score normalized to 0
10	Contributors	project has 10 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
5	Maintained	6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
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
10	Security-Policy	security policy file detected
n/a	Signed-Releases	no releases found
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
9	Vulnerabilities	1 existing vulnerabilities detected

All dependencies 129

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

Registry	Package	Version	Relation
npm	@eslint-community/eslint-utils	`4.10.1`	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.2`	indirect
npm	@humanfs/node	`0.16.8`	indirect
npm	@humanfs/types	`0.15.0`	indirect
npm	@humanwhocodes/module-importer	`1.0.1`	indirect
npm	@humanwhocodes/retry	`0.4.3`	indirect
npm	@metarhia/common	`2.2.2`	indirect
npm	@pkgr/core	`0.3.6`	indirect
npm	@types/estree	`1.0.9`	indirect
npm	@types/json-schema	`7.0.15`	indirect
npm	acorn	`8.18.0`	indirect
npm	acorn-jsx	`5.3.2`	indirect
npm	ajv	`6.15.0`	indirect
npm	ansi-regex	`5.0.1`	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	cliui	`8.0.1`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	color-support	`1.1.3`	indirect
npm	concat-map	`0.0.1`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	debug	`4.4.3`	indirect
npm	deep-is	`0.1.4`	indirect
npm	diff	`4.0.4`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	escalade	`3.2.0`	indirect
npm	escape-string-regexp	`2.0.0`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	eslint	`9.39.5`	indirect
npm	eslint-config-metarhia	`9.2.1`	indirect
npm	eslint-config-prettier	`10.1.8`	indirect
npm	eslint-plugin-prettier	`5.5.6`	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.7.0`	indirect
npm	esrecurse	`4.3.0`	indirect
npm	estraverse	`5.3.0`	indirect
npm	esutils	`2.0.3`	indirect
npm	events-to-array	`1.1.2`	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	fs.realpath	`1.0.0`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	glob	`7.2.3`	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	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	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	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	metatests	`0.9.3`	indirect
npm	minimatch	`3.1.5`	indirect
npm	minipass	`3.3.6`	indirect
npm	ms	`2.1.3`	indirect
npm	natural-compare	`1.4.0`	indirect
npm	once	`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-is-absolute	`1.0.1`	indirect
npm	path-key	`3.1.1`	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	require-directory	`2.1.1`	indirect
npm	resolve-from	`4.0.0`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	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	synckit	`0.11.13`	indirect
npm	tap-mocha-reporter	`5.0.4`	indirect
npm	tap-parser	`11.0.2`	indirect
npm	tap-yaml	`1.0.2`	indirect
npm	type-check	`0.4.0`	indirect
npm	unicode-length	`2.1.0`	indirect
npm	uri-js	`4.4.1`	indirect
npm	which	`2.0.2`	indirect
npm	word-wrap	`1.2.5`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yallist	`4.0.0`	indirect
npm	yaml	`1.10.3`	indirect
npm	yaml	`2.9.0`	indirect
npm	yargs	`17.7.3`	indirect
npm	yargs-parser	`21.1.1`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 129 packages, which also include development and test pins that never ship: 1 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`

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