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

apocas / dockerode

Docker + Node = Dockerode (Node.js module for Docker's Remote API)

JavaScriptApache-2.0★ 4,949 stars⑂ 487 forkssince Aug 2013View on GitHub ↗

apocas/dockerode holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (80/100) and lowest on AI Readiness (57/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

overall / 100

Excellent

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

Ownership

Pedro DiasPersonal account

352 followers91 public repossince Feb 2011team.blue

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	dockerode	5.0.1	25,471,533	102	84 days ago	docker docker.io

Metrics by category

Vitality

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

80Excellent · 21% of overall

Development activity

72Good

How it's scored

36/36	Push recency — last push 4 days ago
11.8/36	Commit cadence — 17/52 weeks with commits
14.7/18	Commit volume — 42 commits in the last year
10/10	OpenSSF Scorecard: Maintained — 11 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10

Inputs used

commits_last_year	42
human_commit_share	0.83
days_since_last_push	4
active_weeks_last_year	17

Release discipline

92Excellent

How it's scored

27/27	Ships releases — 64 releases published
36/36	Release recency — latest release 84 days ago
19.8/27	Release cadence — a release every ~59.6 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	64
latest_release_tag	v5.0.1
releases_from_tags	no
days_since_latest_release	84
mean_days_between_releases	59.6

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?

79Good · 17% of overall

Popularity & adoption

92Excellent

How it's scored

59.9/60	Stars — 4,949 stars
22.4/25	Forks — 487 forks
9.9/15	Watchers — 62 watchers

Inputs used

forks	487
stars	4,949
watchers	62
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 (Apache-2.0)
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	0
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 25,471,533 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	dockerode
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	25,471,533
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?

67Good · 23% of overall

Maintainer resilience (bus factor)

38Weak

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	99
top_contributor_share	0.743

Issue & PR responsiveness

76Good

How it's scored

40.6/42	Issue resolution — 97% of issues closed
25.8/30	PR acceptance — 173/201 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/10 approved changesets -- score normalized to 0

Inputs used

merged_prs	173
open_issues	20
closed_issues	585
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.967
closed_unmerged_prs	28
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

67Good

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
18.3/25	Owner reach — 352 followers of apocas
25/25	Track record — 91 public repos, account ~15 yr old

Inputs used

followers	352
owner_type	User
is_verified	—
owner_login	apocas
public_repos	91
account_age_days	5,705

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

Inputs used

packages	dockerode
ecosystems	npm
any_deprecated	no
min_days_since_publish	84

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall

Engineering practices

84Excellent

How it's scored

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

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	yes
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
10/10	Topics — 5 topics
0/10	Wiki

Inputs used

topics	javascript, docker, nodejs, node, moby
has_wiki	no
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?

66Good · 16% of overall

Security posture

58Moderate

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — no data
2.5/2.5	CI-Tests — 10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 0/10 approved changesets -- score normalized to 0
2.5/2.5	Contributors — project has 23 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
7.5/7.5	Maintained — 11 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5	Packaging — no data
0/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5	SAST — SAST tool is run on all commits
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
4.5/7.5	Vulnerabilities — 4 existing vulnerabilities detected

Inputs used

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

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
25/25	Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	0
affected_packages	0
assessed_packages	65
unassessed_packages	0
affected_by_severity	none
direct_affected_packages	0

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:dockerode@5.0.1 runtime dependency closure — what installing the published package pulls in — 65 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.

57Moderate · 4% of overall

Agent context & guidance

45Weak

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15	Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.docker.com/llms.txt)
30.2/40	Legible commit history — 47 of 83 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	yes
llms_txt_url	https://docs.docker.com/llms.txt
legible_history_share	0.566
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

51Moderate

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
11/11	Lint / format config — .eslintrc
0/11	Static type checking
10/10	Reproducible environment — Dockerfile, lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
8/8	Automated maintenance — 17 of the last 100 commits are automated dependency updates
0/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	yes
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.17

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

Inputs used

primary_language	JavaScript
largest_source_bytes	43,953
source_files_sampled	34
oversized_source_files	0

Machine-readable interfaces

100Exceptional

How it's scored

40/40	API schema (OpenAPI/GraphQL/proto) — lib/proto/auth.proto, lib/proto/buildkit_status.proto
0/20	MCP server — not applicable to this kind of software
40/40	Runnable examples — examples

Inputs used

example_dirs	examples
has_mcp_signal	no
api_schema_files	lib/proto/auth.proto, lib/proto/buildkit_status.proto
interfaces_expected_of	—

Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

4,949GitHub stars

99contributors

42commits, last 12 months

4days since last push

64releases

1bus factor

20open 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 ★ / 487 ⇿

0Stars

487Forks

64Releases

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 4Minor 9Patch 51

Each point covers 12 days.

OpenSSF Scorecard 5.8 / 10

5.8aggregate

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-17 18:17 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
10	CI-Tests	10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 0/10 approved changesets -- score normalized to 0
10	Contributors	project has 23 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
10	Maintained	11 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/a	Packaging	packaging workflow not detected
0	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 0
10	SAST	SAST tool is run on all commits
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
6	Vulnerabilities	4 existing vulnerabilities detected

Direct dependencies 6

Registry	Package	Version constraint	Manifest
npm	@balena/dockerignore	`^1.0.2`	package.json
npm	@grpc/grpc-js	`^1.11.1`	package.json
npm	@grpc/proto-loader	`^0.7.13`	package.json
npm	docker-modem	`^5.0.7`	package.json
npm	protobufjs	`^7.3.2`	package.json
npm	tar-fs	`^2.1.4`	package.json

All dependencies 132

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

Registry	Package	Version	Relation
npm	@balena/dockerignore	`1.0.2`	direct
npm	@grpc/grpc-js	`1.11.4`	direct
npm	@grpc/proto-loader	`0.7.13`	direct
npm	docker-modem	`5.0.7`	direct
npm	protobufjs	`7.6.5`	direct
npm	tar-fs	`2.1.4`	direct
npm	@isaacs/cliui	`8.0.2`	indirect
npm	@js-sdsl/ordered-map	`4.4.2`	indirect
npm	@pkgjs/parseargs	`0.11.0`	indirect
npm	@protobufjs/aspromise	`1.1.2`	indirect
npm	@protobufjs/base64	`1.1.2`	indirect
npm	@protobufjs/codegen	`2.0.5`	indirect
npm	@protobufjs/eventemitter	`1.1.1`	indirect
npm	@protobufjs/fetch	`1.1.1`	indirect
npm	@protobufjs/float	`1.0.2`	indirect
npm	@protobufjs/path	`1.1.2`	indirect
npm	@protobufjs/pool	`1.1.0`	indirect
npm	@protobufjs/utf8	`1.1.1`	indirect
npm	@types/node	`20.14.2`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-regex	`6.2.2`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	ansi-styles	`6.2.3`	indirect
npm	argparse	`2.0.1`	indirect
npm	asn1	`0.2.6`	indirect
npm	assertion-error	`1.1.0`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	base64-js	`1.5.1`	indirect
npm	bcrypt-pbkdf	`1.0.2`	indirect
npm	bl	`4.1.0`	indirect
npm	bluebird	`3.7.2`	indirect
npm	brace-expansion	`2.1.4`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	buffer	`5.7.1`	indirect
npm	buildcheck	`0.0.6`	indirect
npm	camelcase	`6.3.0`	indirect
npm	chai	`4.5.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	check-error	`1.0.3`	indirect
npm	chokidar	`4.0.3`	indirect
npm	chownr	`1.1.4`	indirect
npm	cliui	`8.0.1`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	cpu-features	`0.0.10`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	debug	`4.4.0`	indirect
npm	decamelize	`4.0.0`	indirect
npm	deep-eql	`4.1.4`	indirect
npm	diff	`7.0.0`	indirect
npm	eastasianwidth	`0.2.0`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	emoji-regex	`9.2.2`	indirect
npm	end-of-stream	`1.4.4`	indirect
npm	escalade	`3.1.1`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat	`5.0.2`	indirect
npm	foreground-child	`3.3.1`	indirect
npm	fs-constants	`1.0.0`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-func-name	`2.0.2`	indirect
npm	glob	`10.5.0`	indirect
npm	has-flag	`4.0.0`	indirect
npm	he	`1.2.0`	indirect
npm	ieee754	`1.2.1`	indirect
npm	inherits	`2.0.4`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-path-inside	`3.0.3`	indirect
npm	is-plain-obj	`2.1.0`	indirect
npm	is-unicode-supported	`0.1.0`	indirect
npm	isexe	`2.0.0`	indirect
npm	jackspeak	`3.4.3`	indirect
npm	js-yaml	`4.3.1`	indirect
npm	locate-path	`6.0.0`	indirect
npm	lodash.camelcase	`4.3.0`	indirect
npm	log-symbols	`4.1.0`	indirect
npm	long	`5.3.2`	indirect
npm	loupe	`2.3.7`	indirect
npm	lru-cache	`10.4.3`	indirect
npm	memorystream	`0.3.1`	indirect
npm	minimatch	`9.0.9`	indirect
npm	minipass	`7.1.3`	indirect
npm	mkdirp-classic	`0.5.3`	indirect
npm	mocha	`11.7.5`	indirect
npm	ms	`2.1.3`	indirect
npm	nan	`2.22.0`	indirect
npm	once	`1.4.0`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	package-json-from-dist	`1.0.1`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-scurry	`1.11.1`	indirect
npm	pathval	`1.1.1`	indirect
npm	picocolors	`1.1.1`	indirect
npm	pump	`3.0.0`	indirect
npm	randombytes	`2.1.0`	indirect
npm	readable-stream	`3.6.2`	indirect
npm	readdirp	`4.1.2`	indirect
npm	require-directory	`2.1.1`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	safer-buffer	`2.1.2`	indirect
npm	serialize-javascript	`6.0.2`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	signal-exit	`4.1.0`	indirect
npm	split-ca	`1.0.1`	indirect
npm	ssh2	`1.16.0`	indirect
npm	string-width	`4.2.3`	indirect
npm	string-width	`5.1.2`	indirect
npm	string_decoder	`1.3.0`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-ansi	`7.2.0`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-color	`8.1.1`	indirect
npm	tar-stream	`2.2.0`	indirect
npm	tweetnacl	`0.14.5`	indirect
npm	type-detect	`4.1.0`	indirect
npm	undici-types	`5.26.5`	indirect
npm	util-deprecate	`1.0.2`	indirect
npm	which	`2.0.2`	indirect
npm	workerpool	`9.3.4`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrap-ansi	`8.1.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yargs	`17.7.2`	indirect
npm	yargs-parser	`21.1.1`	indirect
npm	yargs-unparser	`2.0.0`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:dockerode@5.0.1 pulls in 65 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.

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