Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-23 02:26 UTC

crate-ci / clap-cargo

Re-usable CLI flags for `cargo` plugins

RustApache-2.0★ 46 stars⑂ 13 forkssince Apr 2019View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

crate-ci/clap-cargo holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (82/100) and lowest on Sustainability & Governance (60/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

crate-ciOrganization
82 followers27 public repossince Feb 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioclap-cargo0.19.01,023,250324 days agocargo

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
18.7/36Commit cadence27/52 weeks with commits
18/18Commit volume111 commits in the last year
10/10OpenSSF Scorecard: Maintained15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year111
human_commit_share0.61
days_since_last_push2
active_weeks_last_year27
How it's scored
16.2/27Ships releases34 version tags (no GitHub releases)
36/36Release recencylatest release 4 days ago
19.8/27Release cadencea release every ~65.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count34
latest_release_tagv0.19.0
releases_from_tagsyes
days_since_latest_release4
mean_days_between_releases65.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?

64Moderate · 17% of overall
How it's scored
26.8/60Stars46 stars
9/25Forks13 forks
0/15Watchers2 watchers
Inputs used
forks13
stars46
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads1,023,250 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesclap-cargo
dependents
ecosystemscrates
total_downloads12,938,440
monthly_downloads1,023,250
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.7/22.5Commit distributiontop contributor authored 97% of commits
13.5/13.5Contributor breadth11 contributors
10/10OpenSSF Scorecard: Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled11
top_contributor_share0.968
How it's scored
15.3/42Issue resolution36% of issues closed
26.6/30PR acceptance111/125 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/11 approved changesets -- score normalized to 0
Inputs used
merged_prs111
open_issues7
closed_issues4
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.364
closed_unmerged_prs14
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
13.8/25Owner reach82 followers of crate-ci
22.5/25Track record27 public repos, account ~8 yr old
Inputs used
followers82
owner_typeOrganization
is_verifiedno
owner_logincrate-ci
public_repos27
account_age_days3,113

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on crates
35/35Publish recencylatest publish 4 days ago
20/20Version history32 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesclap-cargo
ecosystemscrates
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows7 workflow(s)
24/24Tests present
16/16Linter config.clippy.toml, Cargo.toml ([lints], [workspace.lints])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests19 out of 19 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitedocs.rs/clap-cargo
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagedocs.rs/clap-cargo
docs_sitedocs.rs/clap-cargo
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

77Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests19 out of 19 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 1/11 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
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.5Maintained15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate7.1
Excluded from scoring (no data or not applicable): Branch-Protection, 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
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages44
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 44 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.

72Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history61 of 61 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml, tests/fixtures/mixed_ws/Cargo.toml, tests/fixtures/mixed_ws/a/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config.clippy.toml, Cargo.toml ([lints], [workspace.lints])
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance39 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, tests/fixtures/mixed_ws/Cargo.toml, tests/fixtures/mixed_ws/a/Cargo.toml, tests/fixtures/mixed_ws/c/Cargo.toml, tests/fixtures/pure_ws/Cargo.toml, tests/fixtures/pure_ws/a/Cargo.toml, tests/fixtures/pure_ws/b/Cargo.toml, tests/fixtures/pure_ws/c/Cargo.toml, tests/fixtures/simple/Cargo.toml
dependency_bot_commit_share0.39
How it's scored
45/45Type-checkable codeRust (statically typed)
55/55Manageable file sizes0/13 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes13,755
source_files_sampled13
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
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

46GitHub stars
11contributors
111commits, last 12 months
2days since last push
34releases
1bus factor
7open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 13 ⇿
0Stars
13Forks
29Releases

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.

03581013151312019-042022-122026-08
Major 0Minor 17Patch 12

Each point covers 7 days.

OpenSSF Scorecard 7.1 / 10
7.1aggregate

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-08-23 02:26 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal 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
10CI-Tests19 out of 19 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 1/11 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained15 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
crates.ioanstyle1.0.13Cargo.toml
crates.iocargo_metadata0.23Cargo.toml
crates.ioclap4.5.48Cargo.toml
All dependencies 44

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

RegistryPackageVersionRelation
crates.ioanstyle1.0.14direct
crates.iocargo_metadata0.23.0direct
crates.ioclap4.6.5direct
crates.ioanstream1.0.0indirect
crates.ioanstyle-parse1.0.0indirect
crates.ioanstyle-query1.1.4indirect
crates.ioanstyle-wincon3.0.10indirect
crates.iocamino1.2.1indirect
crates.iocargo-platform0.3.1indirect
crates.ioclap_builder4.6.5indirect
crates.ioclap_derive4.6.4indirect
crates.ioclap_lex1.0.0indirect
crates.iocolorchoice1.0.4indirect
crates.ioheck0.5.0indirect
crates.iois_terminal_polyfill1.70.1indirect
crates.ioitoa1.0.15indirect
crates.iomemchr2.7.6indirect
crates.ioonce_cell_polyfill1.70.1indirect
crates.ioproc-macro21.0.106indirect
crates.ioquote1.0.45indirect
crates.ioryu1.0.20indirect
crates.iosemver1.0.27indirect
crates.ioserde1.0.228indirect
crates.ioserde_core1.0.228indirect
crates.ioserde_derive1.0.228indirect
crates.ioserde_json1.0.145indirect
crates.iostrsim0.11.1indirect
crates.iosyn2.0.117indirect
crates.iosyn3.0.3indirect
crates.iothiserror2.0.17indirect
crates.iothiserror-impl2.0.17indirect
crates.iounicode-ident1.0.19indirect
crates.ioutf8parse0.2.2indirect
crates.iowindows-link0.2.0indirect
crates.iowindows-sys0.60.2indirect
crates.iowindows-targets0.53.4indirect
crates.iowindows_aarch64_gnullvm0.53.0indirect
crates.iowindows_aarch64_msvc0.53.0indirect
crates.iowindows_i686_gnu0.53.0indirect
crates.iowindows_i686_gnullvm0.53.0indirect
crates.iowindows_i686_msvc0.53.0indirect
crates.iowindows_x86_64_gnu0.53.0indirect
crates.iowindows_x86_64_gnullvm0.53.0indirect
crates.iowindows_x86_64_msvc0.53.0indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 44 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

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 statisticscrates.io.