Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 09:47 UTC

BLAKE3-team / BLAKE3

the official Rust and C implementations of the BLAKE3 cryptographic hash function

Assembly · Rust · CApache-2.0★ 6,438 stars⑂ 481 forkssince Nov 2019View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

BLAKE3-team/BLAKE3 holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (87/100) and lowest on AI Readiness (38/100). It was last updated 6 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

BLAKE3 teamOrganization
106 followers3 public repossince Nov 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
crates.ioblake31.8.714,606,5554628 days ago
crates.iob3sum1.8.75,0774628 days ago
crates.iotest_vectorspoints to another repo — not scored0.1.0311405 days ago

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
36/36Push recency — last push 6 days ago
15.2/36Commit cadence — 22/52 weeks with commits
14.2/18Commit volume — 37 commits in the last year
10/10OpenSSF Scorecard: Maintained — 10 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year37
human_commit_share1
days_since_last_push6
active_weeks_last_year22
How it's scored
27/27Ships releases — 33 releases published
36/36Release recency — latest release 28 days ago
19.8/27Release cadence — a release every ~59.8 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count33
latest_release_tag1.8.7
releases_from_tagsno
days_since_latest_release28
mean_days_between_releases59.8

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

87Excellent · 17% of overall
How it's scored
60/60Stars — 6,438 stars
22.3/25Forks — 481 forks
10.5/15Watchers — 80 watchers
Inputs used
forks481
stars6,438
watchers80
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 14,611,632 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesblake3, b3sum
dependents—
ecosystemscrates
total_downloads183,031,282
monthly_downloads14,611,632
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.1/22.5Commit distribution — top contributor authored 64% of commits
13.5/13.5Contributor breadth — 77 contributors
10/10OpenSSF Scorecard: Contributors — project has 19 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled77
top_contributor_share0.638
How it's scored
24.9/42Issue resolution — 59% of issues closed
20.5/30PR acceptance — 136/199 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 10/29 approved changesets -- score normalized to 3
Inputs used
merged_prs136
open_issues123
closed_issues179
prs_merged_7d1
prs_decided_7d2
prs_merged_30d1
prs_decided_30d2
issue_closed_ratio0.593
closed_unmerged_prs63
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
14.6/25Owner reach — 106 followers of BLAKE3-team
16.4/25Track record — 3 public repos, account ~6 yr old
Inputs used
followers106
owner_typeOrganization
is_verifiedno
owner_loginBLAKE3-team
public_repos3
account_age_days2,503

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on crates
35/35Publish recency — latest publish 28 days ago
20/20Version history — 46 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesblake3, b3sum
ecosystemscrates
any_deprecatedno
min_days_since_publish28

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 11 out of 13 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://docs.rs/blake3
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://docs.rs/blake3
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 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
2/2.5CI-Tests — 11 out of 13 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 10/29 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 19 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
7.5/7.5Maintained — 10 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages65
unassessed_packages19
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 65 resolved dependencies against OSV. 19 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.

38Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
20.3/40Legible commit history — 38 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.38
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.toml, b3sum/Cargo.toml, c/blake3_c_rust_bindings/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
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
1/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml, b3sum/Cargo.toml, c/blake3_c_rust_bindings/Cargo.toml, reference_impl/Cargo.toml, test_vectors/Cargo.toml, tools/compiler_version/Cargo.toml, tools/instruction_set_support/Cargo.toml
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Assembly without a type-check config
53.9/55Manageable file sizes — 1/50 source files over 60KB
Inputs used
primary_languageAssembly
largest_source_bytes74,802
source_files_sampled50
oversized_source_files1

Key facts

6,438GitHub stars
77contributors
37commits, last 12 months
6days since last push
33releases
1bus factor
123open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • crates package 'test_vectors' points at a different repository (https://github.com/nathan-at-least/test-vectors); excluded from ecosystem scoring
  • Could not fetch crates package 'reference_impl' from its registry

More detail

Star and fork history 0 ★ / 481 ⇿
0Stars
481Forks
33Releases

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.

0100200300400500461322020-012023-052026-09
Major 1Minor 8Patch 23

Each point covers 7 days.

OpenSSF Scorecard 4.2 / 10
4.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-09-17 09:46 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
8CI-Tests11 out of 13 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 10/29 approved changesets -- score normalized to 3
10Contributorsproject has 19 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained10 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 19
RegistryPackageVersion constraintManifest
crates.ioarrayvec0.7.4Cargo.toml
crates.ioconstant_time_eq0.4.2Cargo.toml
crates.iocfg-if1.0.0Cargo.toml
crates.iodigest0.11.2Cargo.toml
crates.iomemmap20.9Cargo.toml
crates.iorayon-core1.12.1Cargo.toml
crates.ioserde1.0Cargo.toml
crates.iozeroize1Cargo.toml
crates.ioanyhow1.0.25b3sum/Cargo.toml
crates.ioblake31.8.7b3sum/Cargo.toml
crates.ioclap4.0.8b3sum/Cargo.toml
crates.iohex0.4.0b3sum/Cargo.toml
crates.iorayon-core1.12.1b3sum/Cargo.toml
crates.iowild2.0.3b3sum/Cargo.toml
crates.ioblake3—test_vectors/Cargo.toml
crates.iohex0.4.0test_vectors/Cargo.toml
crates.ioreference_impl—test_vectors/Cargo.toml
crates.ioserde1.0test_vectors/Cargo.toml
crates.ioserde_json1.0test_vectors/Cargo.toml
All dependencies 84

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

RegistryPackageVersionRelation
crates.ioanyhow1.0.104direct
crates.ioarrayvec—direct
crates.ioarrayvec0.7.8direct
crates.iocfg-if—direct
crates.iocfg-if1.0.4direct
crates.ioclap4.6.6direct
crates.ioconstant_time_eq—direct
crates.ioconstant_time_eq0.4.2direct
crates.iodigest—direct
crates.iohex—direct
crates.iohex0.4.3direct
crates.iomemmap2—direct
crates.iomemmap20.9.11direct
crates.iorayon-core—direct
crates.iorayon-core1.13.0direct
crates.ioserde—direct
crates.ioserde_json—direct
crates.iowild2.2.1direct
crates.iozeroize—direct
crates.ioanstream1.0.0indirect
crates.ioanstyle1.0.14indirect
crates.ioanstyle-parse1.0.0indirect
crates.ioanstyle-query1.1.5indirect
crates.ioanstyle-wincon3.0.11indirect
crates.iobitflags2.13.1indirect
crates.iocc—indirect
crates.iocc1.4.3indirect
crates.iochacha20—indirect
crates.iociborium—indirect
crates.ioclap_builder4.6.6indirect
crates.ioclap_derive4.6.4indirect
crates.ioclap_lex1.1.0indirect
crates.iocolorchoice1.0.5indirect
crates.iocpufeatures—indirect
crates.iocpufeatures0.3.0indirect
crates.iocrossbeam-deque0.8.7indirect
crates.iocrossbeam-epoch0.9.20indirect
crates.iocrossbeam-utils0.8.22indirect
crates.ioduct1.1.1indirect
crates.ioerrno0.3.14indirect
crates.iofastrand2.5.0indirect
crates.iofind-msvc-tools0.1.11indirect
crates.iogetrandom0.4.3indirect
crates.ioglob0.3.4indirect
crates.ioheck0.5.0indirect
crates.iohmac—indirect
crates.ioignore—indirect
crates.iois_terminal_polyfill1.70.2indirect
crates.iolibc0.2.189indirect
crates.iolinux-raw-sys0.12.1indirect
crates.ioonce_cell1.21.4indirect
crates.ioonce_cell_polyfill1.70.2indirect
crates.ioos_pipe1.2.3indirect
crates.iopage_size—indirect
crates.ioproc-macro21.0.107indirect
crates.ioquote1.0.47indirect
crates.ior-efi6.0.0indirect
crates.iorand—indirect
crates.iorustix1.1.4indirect
crates.ioshared_child1.1.1indirect
crates.ioshared_thread0.2.0indirect
crates.ioshlex2.0.1indirect
crates.iosigchld0.2.4indirect
crates.iosignal-hook0.3.18indirect
crates.iosignal-hook-registry1.4.8indirect
crates.iostrsim0.11.1indirect
crates.iosyn3.0.3indirect
crates.iotempfile—indirect
crates.iotempfile3.27.0indirect
crates.ioterminal_size0.4.4indirect
crates.iounicode-ident1.0.24indirect
crates.ioutf8parse0.2.2indirect
crates.iowindows-link0.2.1indirect
crates.iowindows-sys0.60.2indirect
crates.iowindows-sys0.61.2indirect
crates.iowindows-targets0.53.5indirect
crates.iowindows_aarch64_gnullvm0.53.1indirect
crates.iowindows_aarch64_msvc0.53.1indirect
crates.iowindows_i686_gnu0.53.1indirect
crates.iowindows_i686_gnullvm0.53.1indirect
crates.iowindows_i686_msvc0.53.1indirect
crates.iowindows_x86_64_gnu0.53.1indirect
crates.iowindows_x86_64_gnullvm0.53.1indirect
crates.iowindows_x86_64_msvc0.53.1indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 65 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 19 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.34.0 — full methodology · metrics wiki.

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