Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-23 09:20 UTC

75lb / command-line-usage

A simple, data-driven module for creating a usage guide.

JavaScriptMIT★ 221 stars⑂ 38 forkssince Jun 2015View on GitHub ↗

75lb/command-line-usage holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (78/100) and lowest on Vitality (20/100). It was last updated 204 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 53 is calibrated to 54 on the published index scale (record calibration 2026-08-02).

Ownership

Lloyd BrookesPersonal account

197 followers99 public repossince Dec 201175lb Software Ltd

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	command-line-usage	7.0.4	24,676,776	52	204 days ago	terminal command-line usage generator

Metrics by category

Vitality

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

20At Risk · 21% of overall

Development activity

9Critical

How it's scored

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

Inputs used

commits_last_year	2
human_commit_share	1
days_since_last_push	204
active_weeks_last_year	1

Release discipline

36Weak

How it's scored

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

Inputs used

releases_count	6
latest_release_tag	v7.0.0
releases_from_tags	no
days_since_latest_release	1,297
mean_days_between_releases	493.8

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?

75Good · 17% of overall

Popularity & adoption

51Moderate

How it's scored

38/60	Stars — 221 stars
13.1/25	Forks — 38 forks
0/15	Watchers — 2 watchers

Inputs used

forks	38
stars	221
watchers	2
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

85Excellent

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
18/18	CONTRIBUTING guide
13.5/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	5
has_contributing	yes
has_issue_template	no
has_code_of_conduct	yes
readme_badge_services	badgen.net, github.com
has_pull_request_template	no

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 24,676,776 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	command-line-usage
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	24,676,776
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?

57Moderate · 23% of overall

Maintainer resilience (bus factor)

23At Risk

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	3
top_contributor_share	0.992

Issue & PR responsiveness

62Moderate

How it's scored

42/42	Issue resolution — 100% of issues closed
12/30	PR acceptance — 4/10 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	4
open_issues	0
closed_issues	37
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	1
closed_unmerged_prs	6
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

64Moderate

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
16.5/25	Owner reach — 197 followers of 75lb
25/25	Track record — 99 public repos, account ~14 yr old

Inputs used

followers	197
owner_type	User
is_verified	—
owner_login	75lb
public_repos	99
account_age_days	5,403

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

91Excellent

How it's scored

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

Inputs used

packages	command-line-usage
ecosystems	npm
any_deprecated	no
min_days_since_publish	204

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 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 — package.json ("standard")
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — no data

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	yes
has_precommit_config	no

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

Documentation

75Good

How it's scored

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

Inputs used

topics	—
has_wiki	yes
homepage	—
docs_site	—
has_readme	yes
has_docs_dir	yes
has_description	yes

Security

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

40Weak · 16% of overall

Security posture

25At 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
2.5/2.5	Contributors — project has 4 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/7.5	Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5	Packaging — no data
0/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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 — detected GitHub workflow tokens with excessive permissions
0/7.5	Vulnerabilities — 15 existing vulnerabilities detected

Inputs used

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

Excluded from scoring (no data or not applicable): CI-Tests, 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	11
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:command-line-usage@7.0.4 runtime dependency closure — what installing the published package pulls in — 11 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.

42Weak · 4% of overall

Agent context & guidance

4Critical

How it's scored

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

Verify loop (build / test / typecheck)

43Weak

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
11/11	Lint / format config — package.json ("standard")
0/11	Static type checking
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 — dependency not pinned by hash detected -- score normalized to 0

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

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

Inputs used

primary_language	JavaScript
largest_source_bytes	10,039
source_files_sampled	35
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

221GitHub stars

3contributors

2commits, last 12 months

204days since last push

6releases

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

0Stars

38Forks

6Releases

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

Each point covers 10 days.

OpenSSF Scorecard 2.5 / 10

2.5aggregate

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-23 09:19 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
10	Contributors	project has 4 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
0	Maintained	0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/a	Packaging	packaging workflow not detected
0	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 0
0	SAST	no SAST tool detected
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
0	Vulnerabilities	15 existing vulnerabilities detected

Direct dependencies 4

Registry	Package	Version constraint	Manifest
npm	array-back	`^6.2.2`	package.json
npm	chalk-template	`^0.4.0`	package.json
npm	table-layout	`^4.1.1`	package.json
npm	typical	`^7.3.0`	package.json

All dependencies 165

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

Registry	Package	Version	Relation
npm	array-back	`3.1.0`	direct
npm	array-back	`4.0.2`	direct
npm	array-back	`6.2.2`	direct
npm	chalk-template	`0.4.0`	direct
npm	table-layout	`1.0.2`	direct
npm	table-layout	`4.1.1`	direct
npm	typical	`4.0.0`	direct
npm	typical	`5.2.0`	direct
npm	typical	`7.3.0`	direct
npm	@babel/helper-string-parser	`7.27.1`	indirect
npm	@babel/helper-validator-identifier	`7.28.5`	indirect
npm	@babel/parser	`7.29.0`	indirect
npm	@babel/types	`7.29.0`	indirect
npm	@jridgewell/sourcemap-codec	`1.5.5`	indirect
npm	@jsdoc/salty	`0.2.10`	indirect
npm	@nodelib/fs.scandir	`2.1.5`	indirect
npm	@nodelib/fs.stat	`2.0.5`	indirect
npm	@nodelib/fs.walk	`1.2.8`	indirect
npm	@rollup/plugin-commonjs	`29.0.0`	indirect
npm	@rollup/plugin-node-resolve	`16.0.3`	indirect
npm	@rollup/pluginutils	`5.3.0`	indirect
npm	@rollup/rollup-android-arm-eabi	`4.59.0`	indirect
npm	@rollup/rollup-android-arm64	`4.59.0`	indirect
npm	@rollup/rollup-darwin-arm64	`4.59.0`	indirect
npm	@rollup/rollup-darwin-x64	`4.59.0`	indirect
npm	@rollup/rollup-freebsd-arm64	`4.59.0`	indirect
npm	@rollup/rollup-freebsd-x64	`4.59.0`	indirect
npm	@rollup/rollup-linux-arm-gnueabihf	`4.59.0`	indirect
npm	@rollup/rollup-linux-arm-musleabihf	`4.59.0`	indirect
npm	@rollup/rollup-linux-arm64-gnu	`4.59.0`	indirect
npm	@rollup/rollup-linux-arm64-musl	`4.59.0`	indirect
npm	@rollup/rollup-linux-loong64-gnu	`4.59.0`	indirect
npm	@rollup/rollup-linux-loong64-musl	`4.59.0`	indirect
npm	@rollup/rollup-linux-ppc64-gnu	`4.59.0`	indirect
npm	@rollup/rollup-linux-ppc64-musl	`4.59.0`	indirect
npm	@rollup/rollup-linux-riscv64-gnu	`4.59.0`	indirect
npm	@rollup/rollup-linux-riscv64-musl	`4.59.0`	indirect
npm	@rollup/rollup-linux-s390x-gnu	`4.59.0`	indirect
npm	@rollup/rollup-linux-x64-gnu	`4.59.0`	indirect
npm	@rollup/rollup-linux-x64-musl	`4.59.0`	indirect
npm	@rollup/rollup-openbsd-x64	`4.59.0`	indirect
npm	@rollup/rollup-openharmony-arm64	`4.59.0`	indirect
npm	@rollup/rollup-win32-arm64-msvc	`4.59.0`	indirect
npm	@rollup/rollup-win32-ia32-msvc	`4.59.0`	indirect
npm	@rollup/rollup-win32-x64-gnu	`4.59.0`	indirect
npm	@rollup/rollup-win32-x64-msvc	`4.59.0`	indirect
npm	@test-runner/core	`0.10.0`	indirect
npm	@test-runner/default-view	`0.6.1`	indirect
npm	@test-runner/live-view	`0.2.1`	indirect
npm	@test-runner/oneline-view	`0.2.0`	indirect
npm	@test-runner/tom	`0.8.1`	indirect
npm	@test-runner/tom	`0.9.1`	indirect
npm	@types/estree	`1.0.8`	indirect
npm	@types/linkify-it	`5.0.0`	indirect
npm	@types/markdown-it	`14.1.2`	indirect
npm	@types/mdurl	`2.0.0`	indirect
npm	@types/resolve	`1.20.2`	indirect
npm	ansi-escape-sequences	`6.2.4`	indirect
npm	ansi-regex	`6.2.2`	indirect
npm	ansi-styles	`3.2.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	argparse	`2.0.1`	indirect
npm	bluebird	`3.7.2`	indirect
npm	braces	`3.0.3`	indirect
npm	cache-point	`3.0.1`	indirect
npm	catharsis	`0.9.0`	indirect
npm	chalk	`2.4.2`	indirect
npm	chalk	`4.1.2`	indirect
npm	char-regex	`2.0.2`	indirect
npm	color-convert	`1.9.3`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.3`	indirect
npm	color-name	`1.1.4`	indirect
npm	command-line-args	`5.2.1`	indirect
npm	command-line-args	`6.0.1`	indirect
npm	command-line-usage	`6.1.3`	indirect
npm	command-line-usage	`7.0.3`	indirect
npm	common-sequence	`3.0.0`	indirect
npm	commondir	`1.0.1`	indirect
npm	composite-class	`2.0.1`	indirect
npm	config-master	`3.1.0`	indirect
npm	create-mixin	`3.0.0`	indirect
npm	current-module-paths	`1.1.3`	indirect
npm	deep-extend	`0.6.0`	indirect
npm	deepmerge	`4.3.1`	indirect
npm	dmd	`7.1.1`	indirect
npm	entities	`4.5.0`	indirect
npm	escape-string-regexp	`1.0.5`	indirect
npm	escape-string-regexp	`2.0.0`	indirect
npm	estree-walker	`2.0.2`	indirect
npm	fast-glob	`3.3.3`	indirect
npm	fastq	`1.20.1`	indirect
npm	fdir	`6.5.0`	indirect
npm	file-set	`5.3.0`	indirect
npm	fill-range	`7.1.1`	indirect
npm	find-replace	`3.0.0`	indirect
npm	find-replace	`5.0.2`	indirect
npm	fsevents	`2.3.3`	indirect
npm	fsm-base	`0.7.0`	indirect
npm	function-bind	`1.1.2`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	graceful-fs	`4.2.11`	indirect
npm	handlebars	`4.7.8`	indirect
npm	has-flag	`3.0.0`	indirect
npm	has-flag	`4.0.0`	indirect
npm	hasown	`2.0.2`	indirect
npm	is-core-module	`2.16.1`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-module	`1.0.0`	indirect
npm	is-number	`7.0.0`	indirect
npm	is-reference	`1.2.1`	indirect
npm	js2xmlparser	`4.0.2`	indirect
npm	jsdoc	`4.0.5`	indirect
npm	jsdoc-api	`9.3.5`	indirect
npm	jsdoc-parse	`6.2.5`	indirect
npm	jsdoc-to-markdown	`9.1.3`	indirect
npm	klaw	`3.0.0`	indirect
npm	linkify-it	`5.0.0`	indirect
npm	load-module	`4.2.1`	indirect
npm	lodash	`4.17.23`	indirect
npm	lodash.camelcase	`4.3.0`	indirect
npm	magic-string	`0.30.21`	indirect
npm	markdown-it	`14.1.1`	indirect
npm	markdown-it-anchor	`8.6.7`	indirect
npm	marked	`4.3.0`	indirect
npm	mdurl	`2.0.0`	indirect
npm	merge2	`1.4.1`	indirect
npm	micromatch	`4.0.8`	indirect
npm	minimist	`1.2.8`	indirect
npm	mkdirp	`1.0.4`	indirect
npm	neo-async	`2.6.2`	indirect
npm	object-to-spawn-args	`2.0.1`	indirect
npm	obso	`0.7.0`	indirect
npm	path-parse	`1.0.7`	indirect
npm	picomatch	`2.3.1`	indirect
npm	picomatch	`4.0.3`	indirect
npm	punycode.js	`2.3.1`	indirect
npm	queue-microtask	`1.2.3`	indirect
npm	race-timeout-anywhere	`2.0.0`	indirect
npm	reduce-flatten	`2.0.0`	indirect
npm	requizzle	`0.2.4`	indirect
npm	resolve	`1.22.11`	indirect
npm	reusify	`1.1.0`	indirect
npm	rollup	`4.59.0`	indirect
npm	run-parallel	`1.2.0`	indirect
npm	sort-array	`5.1.1`	indirect
npm	source-map	`0.6.1`	indirect
npm	string-length	`5.0.1`	indirect
npm	strip-ansi	`7.2.0`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	supports-color	`5.5.0`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-preserve-symlinks-flag	`1.0.0`	indirect
npm	test-runner	`0.10.1`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	uc.micro	`2.1.0`	indirect
npm	uglify-js	`3.19.3`	indirect
npm	underscore	`1.13.8`	indirect
npm	walk-back	`2.0.1`	indirect
npm	walk-back	`5.1.1`	indirect
npm	wordwrap	`1.0.0`	indirect
npm	wordwrapjs	`4.0.1`	indirect
npm	wordwrapjs	`5.1.1`	indirect
npm	xmlcreate	`2.0.4`	indirect

Dependency advisories 0

Installing npm:command-line-usage@7.0.4 pulls in 11 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