Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-04 19:50 UTC

RustCrypto / traits

Collection of cryptography-related traits

RustNo license detected★ 750 stars⑂ 251 forkssince Mar 2017View on GitHub ↗

RustCrypto/traits holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (74/100) and lowest on Security (47/100). It was last updated today. A single contributor accounts for most of its recent work.

34
overall / 100
At Risk

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.

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)
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 62 is calibrated to 69 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 75% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

Rust CryptoOrganization
2,344 followers40 public repossince Sep 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iokdf0.1.028,1554183 days agocryptocryptographyno-std
crates.iokem0.3.0913,96323123 days agocryptocryptographyno-std
crates.ioaead0.6.114,276,2373248 days agocryptoencryptioncryptographyno-std
crates.iocipher0.5.223,858,3803977 days agoblock-ciphercryptostream-ciphertraitcryptographyno-std
crates.iocrypto0.5.1102,38391133 days agoencryptionrustcryptocryptono-stdcryptography
crates.iodigest0.11.379,089,9046993 days agocryptodigesthashcryptographyno-std
crates.iosignature3.0.031,733,2645594 days agocryptoecdsaed25519signaturesigningcryptographyno-std
crates.iocrypto-common0.2.274,914,6273577 days agocryptotraitscryptographyno-std

Metrics by category

Vitality

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

58Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
32.5/36Commit cadence47/52 weeks with commits
18/18Commit volume425 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year425
human_commit_share0.85
days_since_last_push0
active_weeks_last_year47
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

63Moderate · 17% of overall
How it's scored
46.6/60Stars750 stars
20/25Forks251 forks
6.5/15Watchers16 watchers
Inputs used
forks251
stars750
watchers16
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges10
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads224,916,913 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageskdf, kem, aead, cipher, crypto, digest, signature, crypto-common
dependents
ecosystemscrates
total_downloads2,520,198,181
monthly_downloads224,916,913
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?

74Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5.4/22.5Commit distributiontop contributor authored 76% of commits
13.5/13.5Contributor breadth72 contributors
10/10OpenSSF Scorecard: Contributorsproject has 18 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled72
top_contributor_share0.761
How it's scored
36.7/42Issue resolution87% of issues closed
25.2/30PR acceptance1,808/2,152 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 4/26 approved changesets -- score normalized to 1
Inputs used
merged_prs1,808
open_issues39
closed_issues269
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d2
issue_closed_ratio0.873
closed_unmerged_prs344
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
24.2/25Owner reach2,344 followers of RustCrypto
23.7/25Track record40 public repos, account ~9 yr old
Inputs used
followers2,344
owner_typeOrganization
is_verified
owner_loginRustCrypto
public_repos40
account_age_days3,604
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable8 package(s) on crates
35/35Publish recencylatest publish 48 days ago
20/20Version history69 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageskdf, kem, aead, cipher, crypto, digest, signature, crypto-common
ecosystemscrates
any_deprecatedno
min_days_since_publish48

Engineering Quality

Are baseline engineering and documentation practices in place?

63Moderate · 19% of overall
How it's scored
24/24CI workflows14 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/kdf
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_sitehttps://docs.rs/kdf
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

47Weak · 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-Tests30 out of 30 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.8/7.5Code-ReviewFound 4/26 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 18 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.2
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier75
security_posture_after_multiplier46
security_posture_before_jurisdiction62
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 75% multiplier and gives Security posture an At risk ceiling of 34.

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_packages45
unassessed_packages32
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 45 resolved dependencies against OSV. 32 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

68Good · 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 history84 of 85 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.988
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml, aead/Cargo.toml, cipher/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance15 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_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, aead/Cargo.toml, cipher/Cargo.toml, crypto-common/Cargo.toml, crypto/Cargo.toml, digest/Cargo.toml, elliptic-curve/Cargo.toml, kdf/Cargo.toml, kem/Cargo.toml, password-hash/Cargo.toml, signature/Cargo.toml, universal-hash/Cargo.toml
dependency_bot_commit_share0.15
How it's scored
45/45Type-checkable codeRust (statically typed)
55/55Manageable file sizes0/75 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes25,050
source_files_sampled75
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

750GitHub stars
72contributors
425commits, last 12 months
0days since last push
0releases
1bus factor
39open 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 ★ / 251 ⇿
0Stars
251Forks

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.

05010015020025024782017-112022-032026-07

Each point covers 8 days.

OpenSSF Scorecard 6.2 / 10
6.2aggregate

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-04 19:49 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-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/26 approved changesets -- score normalized to 1
10Contributorsproject has 18 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 52
RegistryPackageVersion constraintManifest
crates.iocommon0.2aead/Cargo.toml
crates.ioinout0.2.2aead/Cargo.toml
crates.ioarrayvec0.7aead/Cargo.toml
crates.ioblobby0.4aead/Cargo.toml
crates.iobytes1.11.1aead/Cargo.toml
crates.iocommon0.2.2cipher/Cargo.toml
crates.ioinout0.2.2cipher/Cargo.toml
crates.ioblobby0.4cipher/Cargo.toml
crates.ioblock-buffer0.12cipher/Cargo.toml
crates.iozeroize1.8cipher/Cargo.toml
crates.iohybrid-array0.4.7crypto-common/Cargo.toml
crates.iogetrandom0.4crypto-common/Cargo.toml
crates.iorand_core0.10crypto-common/Cargo.toml
crates.iocommon0.2crypto/Cargo.toml
crates.ioaead0.6.0-rc.5crypto/Cargo.toml
crates.iocipher0.5crypto/Cargo.toml
crates.iodigest0.11crypto/Cargo.toml
crates.ioelliptic-curve0.14.0-rc.17crypto/Cargo.toml
crates.iopassword-hash0.6.0-rc.6crypto/Cargo.toml
crates.iosignature3.0.0-rc.6crypto/Cargo.toml
crates.iouniversal-hash0.6.0-rc.4crypto/Cargo.toml
crates.iocommon0.2digest/Cargo.toml
crates.ioblock-buffer0.12digest/Cargo.toml
crates.ioblobby0.4digest/Cargo.toml
crates.ioconst-oid0.10digest/Cargo.toml
crates.ioctutils0.4digest/Cargo.toml
crates.iozeroize1.7digest/Cargo.toml
crates.ioarray0.4.13elliptic-curve/Cargo.toml
crates.iobigint0.7.5elliptic-curve/Cargo.toml
crates.iobase16ct1elliptic-curve/Cargo.toml
crates.iocommon0.2elliptic-curve/Cargo.toml
crates.iorand_core0.10elliptic-curve/Cargo.toml
crates.iosubtle2.6elliptic-curve/Cargo.toml
crates.iozeroize1.7elliptic-curve/Cargo.toml
crates.iodigest0.11elliptic-curve/Cargo.toml
crates.ioff0.14elliptic-curve/Cargo.toml
crates.iogroup0.14elliptic-curve/Cargo.toml
crates.iohkdf0.13elliptic-curve/Cargo.toml
crates.iohex-literal1elliptic-curve/Cargo.toml
crates.iopem-rfc74681elliptic-curve/Cargo.toml
crates.iopkcs80.11elliptic-curve/Cargo.toml
crates.iosec10.8elliptic-curve/Cargo.toml
crates.ioserdect0.4elliptic-curve/Cargo.toml
crates.iocommon0.2kem/Cargo.toml
crates.iorand_core0.10kem/Cargo.toml
crates.iogetrandom0.4password-hash/Cargo.toml
crates.iophc0.6password-hash/Cargo.toml
crates.iorand_core0.10password-hash/Cargo.toml
crates.iodigest0.11signature/Cargo.toml
crates.iorand_core0.10signature/Cargo.toml
crates.ioctutils0.4universal-hash/Cargo.toml
crates.iocommon0.2universal-hash/Cargo.toml
All dependencies 77

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

RegistryPackageVersionRelation
crates.ioaeaddirect
crates.ioarrayvecdirect
crates.ioarrayvec0.7.8direct
crates.iobase16ctdirect
crates.iobase16ct1.0.0direct
crates.ioblobbydirect
crates.ioblobby0.4.0direct
crates.ioblock-bufferdirect
crates.ioblock-buffer0.12.1direct
crates.iobytesdirect
crates.iobytes1.12.1direct
crates.iocipherdirect
crates.ioconst-oiddirect
crates.ioconst-oid0.10.2direct
crates.ioctutilsdirect
crates.ioctutils0.4.2direct
crates.iodigestdirect
crates.ioelliptic-curvedirect
crates.ioffdirect
crates.ioff0.14.0direct
crates.iogetrandomdirect
crates.iogetrandom0.4.3direct
crates.iogroupdirect
crates.iogroup0.14.0direct
crates.iohex-literaldirect
crates.iohex-literal1.1.0direct
crates.iohkdfdirect
crates.iohkdf0.13.0direct
crates.iohybrid-arraydirect
crates.iohybrid-array0.4.13direct
crates.ioinoutdirect
crates.ioinout0.2.2direct
crates.iopassword-hashdirect
crates.iopem-rfc7468direct
crates.iopem-rfc74681.0.0direct
crates.iophcdirect
crates.iophc0.6.1direct
crates.iopkcs8direct
crates.iopkcs80.11.0direct
crates.iorand_coredirect
crates.iorand_core0.10.1direct
crates.iosec1direct
crates.iosec10.8.1direct
crates.ioserdectdirect
crates.ioserdect0.4.3direct
crates.iosignaturedirect
crates.iosubtledirect
crates.iosubtle2.6.1direct
crates.iouniversal-hashdirect
crates.iozeroizedirect
crates.iozeroize1.9.0direct
crates.ioautocfg1.5.1indirect
crates.iobase64ct1.8.3indirect
crates.ioblock-padding0.4.2indirect
crates.iocfg-if1.0.4indirect
crates.iocmov0.5.4indirect
crates.iocpubits0.1.1indirect
crates.iocpufeatures0.3.0indirect
crates.iocrypto-bigintindirect
crates.iocrypto-bigint0.7.5indirect
crates.iocrypto-commonindirect
crates.ioder0.8.1indirect
crates.iohmac0.13.0indirect
crates.iolibc0.2.186indirect
crates.ionum-traits0.2.19indirect
crates.ioproc-macro21.0.106indirect
crates.ioquote1.0.46indirect
crates.ior-efi6.0.0indirect
crates.ioserde1.0.228indirect
crates.ioserde_core1.0.228indirect
crates.ioserde_derive1.0.228indirect
crates.iosha2indirect
crates.iosha20.11.0indirect
crates.iospki0.8.0indirect
crates.iosyn2.0.118indirect
crates.iotypenum1.20.1indirect
crates.iounicode-ident1.0.24indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 45 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 32 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io.