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
qdrant/qdrant 3 adequate · 2 strong Rust 929,010 lines 35,439 2026-10-25 adequate
tinyhumansai/openhuman 1 adequate · 2 strong Rust 1,477,231 lines 42,253 2026-10-23 adequate
tokio-rs/tokio 3 strong Rust 196,074 lines 33,277 2026-10-25 adequate
surrealdb/surrealdb 3 adequate · 2 strong Rust 630,012 lines 33,086 2026-10-25 adequate
codewhale-hq/codewhale 3 adequate · 2 strong Rust 1,559,320 lines 41,157 2026-10-23 adequate
postgresml/postgresml 4 adequate · 1 strong Rust 96,274 lines 6,826 2026-11-08 adequate
atuinsh/atuin 3 adequate · 2 strong Rust 157,273 lines 31,862 2026-10-25 adequate
koharu-rs/koharu 2 adequate · 2 strong Rust 180,296 lines 6,578 2026-11-08 adequate
reacherhq/check-if-email-exists 3 adequate · 2 strong Rust 15,458 lines 10,404 2026-11-03 adequate
tabbyml/tabby 3 adequate · 1 strong Rust 165,247 lines 33,924 2026-10-23 adequate
tokio-rs/axum 2 adequate · 2 strong Rust 57,171 lines 27,258 2026-10-25 adequate
trailbaseio/trailbase 4 adequate · 1 strong Rust 190,433 lines 5,721 2026-11-08 adequate
databendlabs/databend 3 adequate · 2 strong Rust 1,303,500 lines 9,491 2026-11-03 adequate
pgdogdev/pgdog 2 adequate · 3 strong Rust 227,298 lines 5,594 2026-11-08 adequate
restatedev/restate 3 adequate · 2 strong Rust 379,109 lines 4,594 2026-11-08 adequate
katanemo/plano 3 adequate · 2 strong Rust 103,798 lines 7,107 2026-11-03 adequate
rivet-dev/rivet 2 adequate · 2 strong Rust 494,930 lines 6,564 2026-11-03 adequate
spinframework/spin 3 adequate · 2 strong Rust 104,905 lines 6,565 2026-11-03 adequate
materializeinc/materialize 3 adequate · 2 strong Rust 1,808,273 lines 6,392 2026-11-03 adequate
helixdb/helix-db 2 adequate · 3 strong Rust 760,616 lines 6,267 2026-11-03 adequate
scanopy/scanopy 4 adequate · 1 strong Rust 665,851 lines 5,932 2026-11-03 adequate
eclipse-zenoh/zenoh 1 adequate · 2 strong Rust 224,709 lines 3,317 2026-11-07 adequate
arroyosystems/arroyo 3 adequate · 2 strong Rust 142,558 lines 5,077 2026-11-03 adequate
lemmynet/lemmy 3 adequate · 2 strong Rust 134,751 lines 14,614 2026-10-25 adequate
getzola/zola 2 adequate · 2 strong Rust 43,441 lines 17,550 2026-10-23 adequate
ironcalc/ironcalc 3 adequate · 2 strong Rust 231,339 lines 4,246 2026-11-03 adequate
donutbrowser/donutbrowser 3 adequate · 2 strong Rust 422,900 lines 4,205 2026-11-03 adequate
serde-rs/serde 1 adequate · 2 strong Rust 43,784 lines 10,831 2026-10-25 adequate
linkerd/linkerd2-proxy 2 adequate · 2 strong Rust 106,971 lines 2,146 2026-11-08 adequate
rustic-rs/rustic 4 adequate · 1 strong Rust 18,707 lines 3,364 2026-11-03 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.