Rust repositories reading adequate

Every public repository surveyed, browsable and searchable. Including the unflattering ones — a tool that only published good results would be a badge vending machine, not a diligence instrument.

All bands Strong Adequate 86 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
rustic-rs/rustic 4 adequate · 1 strong Rust 18,707 lines 3,364 2026-11-03 adequate
moltis-org/moltis 2 adequate · 2 strong Rust 803,386 lines 2,939 2026-11-03 adequate
cnosdb/cnosdb 2 adequate · 2 strong Rust 161,412 lines 1,754 2026-11-07 adequate
numaproj/numaflow 4 adequate · 1 strong Rust 337,575 lines 2,837 2026-11-03 adequate
rustls/rustls 1 adequate · 2 strong Rust 88,522 lines 7,647 2026-10-25 adequate
attify/firmware-analysis-toolkit 1 adequate · 2 strong Rust 249,207 lines 1,622 2026-11-08 adequate
risingwavelabs/risingwave 3 adequate · 2 strong Rust 1,196,119 lines 9,399 2026-10-23 adequate
parseablehq/parseable 4 adequate · 1 strong Rust 95,920 lines 2,570 2026-11-03 adequate
quarylabs/quary 2 adequate · 2 strong Rust 141,862 lines 2,386 2026-11-03 adequate
juspay/hyperswitch-prism 3 adequate · 2 strong Rust 1,164,868 lines 1,392 2026-11-08 adequate
fkie-cad/cwe_checker 1 adequate · 2 strong Rust 59,414 lines 1,364 2026-11-08 adequate
meteroid-oss/meteroid 4 adequate · 1 strong Rust 351,598 lines 1,343 2026-11-07 adequate
moonrepo/moon 2 adequate · 2 strong Rust 196,487 lines 4,169 2026-10-28 adequate
fastcrw/crw 3 adequate · 1 strong Rust 262,618 lines 1,214 2026-11-08 adequate
kanidm/kanidm 3 adequate · 2 strong Rust 448,893 lines 5,431 2026-10-25 adequate
greptimeteam/greptimedb 3 adequate · 2 strong Rust 1,165,036 lines 6,760 2026-10-23 adequate
eventual-inc/daft 3 adequate · 2 strong Rust 514,233 lines 5,810 2026-10-23 adequate
slothflowlabs/duckle 3 adequate · 2 strong Rust 240,358 lines 1,548 2026-11-03 adequate
deuxfleurs-org/garage 2 adequate · 2 strong Rust 98,226 lines 4,756 2026-10-23 adequate
build-trust/ockam 3 strong Rust 245,908 lines 4,639 2026-10-23 adequate
slatedb/slatedb 2 adequate · 2 strong Rust 242,643 lines 3,582 2026-10-23 adequate
svix/svix-webhooks 3 adequate · 2 strong Rust 277,348 lines 3,462 2026-10-23 adequate
codeberg.org/forgejo-contrib/forgejo-cli 2 adequate · 1 strong Rust 20,069 lines 557 2026-11-07 adequate
codeberg.org/simonrepp/faircamp 3 adequate · 1 strong Rust 81,786 lines 426 2026-11-08 adequate
artifact-keeper/artifact-keeper 4 adequate · 1 strong Rust 1,024,594 lines 1,208 2026-10-28 adequate
codeberg.org/mergiraf/mergiraf 3 adequate · 1 strong Rust 39,243 lines 456 2026-10-25 adequate

What a band means. A band sums up one reading of one commit: strong, adequate or significant findings. Here it counts the project's code, process, product, security and operations. A report reads more than that, so its band can differ from its row.

How listing works. Every public repository surveyed is listed — assessing public work is commentary on public work, and a library that hid the small ones would be quietly editorialising about which code counts. Private repositories are never listed. Anyone who proves control of a repo can attach a response to a finding, request a re-run, or delist it. Delisting is immediate and no-questions. An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev. There is no org-level score. Repositories are listed one by one, and sorting by band orders them by their own readings. Takedown: one email, 48 hours.