Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-23 09:03 UTC

75lb / command-line-args

A mature, feature-complete library to parse command-line options.

JavaScriptMIT★ 719 stars⑂ 103 forkssince May 2014View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

75lb/command-line-args holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Community & Adoption (81/100) and lowest on AI Readiness (33/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.

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

65
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 60 is calibrated to 65 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

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmcommand-line-args6.0.227,894,90676183 days agoargvparseargumentargsoptionoptionsparserparsingclicommandline

Metrics by category

Vitality

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

39Weak · 21% of overall
How it's scored
36/36Push recency — last push 6 days ago
0.7/36Commit cadence — 1/52 weeks with commits
4.3/18Commit volume — 2 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year2
human_commit_share1
days_since_last_push6
active_weeks_last_year1
How it's scored
27/27Ships releases — 8 releases published
0/36Release recency — latest release 809 days ago
5.4/27Release cadence — a release every ~455.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count8
latest_release_tagv6.0.0
releases_from_tagsno
days_since_latest_release809
mean_days_between_releases455.5
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?

81Excellent · 17% of overall
How it's scored
46.3/60Stars — 719 stars
16.7/25Forks — 103 forks
3.3/15Watchers — 5 watchers
Inputs used
forks103
stars719
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadgen.net, github.com
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 27,894,906 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagescommand-line-args
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads27,894,906
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
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.7/22.5Commit distribution — top contributor authored 97% of commits
13.5/13.5Contributor breadth — 10 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled10
top_contributor_share0.967
How it's scored
39.3/42Issue resolution — 94% of issues closed
18.2/30PR acceptance — 17/28 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 5/23 approved changesets -- score normalized to 2
Inputs used
merged_prs17
open_issues7
closed_issues103
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.936
closed_unmerged_prs11
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
16.5/25Owner reach — 197 followers of 75lb
25/25Track record — 99 public repos, account ~14 yr old
Inputs used
followers197
owner_typeUser
is_verified—
owner_login75lb
public_repos99
account_age_days5,403
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on npm
26/35Publish recency — latest publish 183 days ago
20/20Version history — 76 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescommand-line-args
ecosystemsnpm
any_deprecatedno
min_days_since_publish183

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — package.json ("standard")
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 5 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 6 topics
10/10Wiki
Inputs used
topicsgetopt, argv, option-parser, npm-package, nodejs-modules, command-line-parser
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

52Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 5 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 5/23 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 4 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4
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 advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages4
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:command-line-args@6.0.2 runtime dependency closure — what installing the published package pulls in — 4 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.

33At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
7.5/40Legible commit history — 14 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.14
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — package.json ("standard")
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/42 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes12,382
source_files_sampled42
oversized_source_files0

Key facts

719GitHub stars
10contributors
2commits, last 12 months
6days since last push
8releases
1bus factor
7open 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 ★ / 103 ⇿
0Stars
103Forks
8Releases

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.

02040608010012010132015-092020-112026-02
Major 5Minor 3Patch 0

Each point covers 10 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-23 09:02 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 5 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 5/23 approved changesets -- score normalized to 2
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npmarray-back^6.2.3package.json
npmfind-replace^5.0.2package.json
npmlodash.camelcase^4.3.0package.json
npmtypical^7.3.0package.json
All dependencies 61

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

RegistryPackageVersionRelation
npmarray-back3.1.0direct
npmarray-back4.0.2direct
npmarray-back6.2.3direct
npmfind-replace3.0.0direct
npmfind-replace5.0.2direct
npmlodash.camelcase4.3.0direct
npmtypical4.0.0direct
npmtypical5.2.0direct
npmtypical7.3.0direct
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@test-runner/core0.10.0indirect
npm@test-runner/default-view0.6.1indirect
npm@test-runner/live-view0.2.1indirect
npm@test-runner/oneline-view0.2.0indirect
npm@test-runner/tom0.8.1indirect
npm@test-runner/tom0.9.1indirect
npmansi-escape-sequences6.2.3indirect
npmansi-regex6.1.0indirect
npmansi-styles3.2.1indirect
npmbraces3.0.3indirect
npmchalk2.4.2indirect
npmchar-regex2.0.1indirect
npmcolor-convert1.9.3indirect
npmcolor-name1.1.3indirect
npmcommand-line-args5.2.1indirect
npmcommand-line-usage6.1.3indirect
npmcomposite-class2.0.1indirect
npmcreate-mixin3.0.0indirect
npmcurrent-module-paths1.1.2indirect
npmdeep-extend0.6.0indirect
npmescape-string-regexp1.0.5indirect
npmfast-glob3.3.2indirect
npmfastq1.17.1indirect
npmfile-set5.2.2indirect
npmfill-range7.1.1indirect
npmfsm-base0.7.0indirect
npmglob-parent5.1.2indirect
npmhas-flag3.0.0indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmload-module4.2.1indirect
npmmerge21.4.1indirect
npmmicromatch4.0.8indirect
npmobso0.7.0indirect
npmpicomatch2.3.1indirect
npmqueue-microtask1.2.3indirect
npmrace-timeout-anywhere2.0.0indirect
npmreduce-flatten2.0.0indirect
npmreusify1.0.4indirect
npmrun-parallel1.2.0indirect
npmstring-length5.0.1indirect
npmstrip-ansi7.1.0indirect
npmsupports-color5.5.0indirect
npmtable-layout1.0.2indirect
npmtest-runner0.10.1indirect
npmto-regex-range5.0.1indirect
npmwalk-back5.1.1indirect
npmwordwrapjs4.0.1indirect
Dependency advisories 0

Installing npm:command-line-args@6.0.2 pulls in 4 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.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.