Rust repositories reading strong

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 36 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
rustdesk/rustdesk 2 adequate · 3 strong Rust 295,034 lines 124,631 2026-10-25 strong
tauri-apps/tauri 2 adequate · 3 strong Rust 172,589 lines 111,445 2026-10-25 strong
denoland/deno 1 adequate · 3 strong Rust 1,285,691 lines 108,504 2026-10-25 strong
astral-sh/uv 1 adequate · 3 strong Rust 579,805 lines 90,174 2026-10-25 strong
memvid/memvid 2 adequate · 3 strong Rust 78,353 lines 16,608 2026-11-07 strong
tursodatabase/turso 1 adequate · 3 strong Rust 1,056,899 lines 25,131 2026-11-03 strong
dbt-labs/dbt 1 adequate · 3 strong Rust 930,336 lines 14,063 2026-11-07 strong
starship/starship 1 adequate · 3 strong Rust 230,693 lines 60,082 2026-10-25 strong
cocoindex-io/cocoindex 4 strong Rust 247,431 lines 11,745 2026-11-07 strong
aaif-goose/goose 2 adequate · 3 strong Rust 610,585 lines 55,587 2026-10-23 strong
nushell/nushell 1 adequate · 3 strong Rust 482,405 lines 40,580 2026-10-25 strong
casey/just 1 adequate · 3 strong Rust 76,062 lines 36,039 2026-10-25 strong
firecracker-microvm/firecracker 1 adequate · 4 strong Rust 228,438 lines 37,583 2026-10-23 strong
falkordb/falkordb 1 adequate · 3 strong Rust 272,760 lines 10,502 2026-11-03 strong
redisearch/redisearch 1 adequate · 3 strong Rust 653,101 lines 6,247 2026-11-07 strong
agentgateway/agentgateway 2 adequate · 3 strong Rust 592,107 lines 5,907 2026-11-08 strong
influxdata/influxdb 1 adequate · 4 strong Rust 420,633 lines 31,780 2026-10-23 strong
gitbutlerapp/gitbutler 1 adequate · 3 strong Rust 689,361 lines 21,750 2026-10-25 strong
chroma-core/chroma 2 adequate · 3 strong Rust 519,579 lines 29,554 2026-10-22 strong
windmill-labs/windmill 2 adequate · 3 strong Rust 1,548,413 lines 18,070 2026-10-25 strong
zensical/zensical 2 adequate · 3 strong Rust 100,183 lines 6,071 2026-11-03 strong
neondatabase/neon 2 adequate · 3 strong Rust 457,599 lines 23,246 2026-10-22 strong
cube-js/cube 1 adequate · 4 strong Rust 963,250 lines 21,061 2026-10-22 strong
fluvio-community/fluvio 1 adequate · 4 strong Rust 172,309 lines 5,259 2026-11-03 strong
paradedb/paradedb 2 adequate · 3 strong Rust 345,084 lines 9,453 2026-10-28 strong
typedb/typedb 2 adequate · 3 strong Rust 191,149 lines 4,500 2026-11-03 strong
deeplethe/utopia 2 adequate · 3 strong Rust 366,732 lines 8,581 2026-10-28 strong
lance-format/lance 1 adequate · 3 strong Rust 1,273,332 lines 7,224 2026-10-28 strong
lancedb/lancedb 1 adequate · 4 strong Rust 307,285 lines 11,754 2026-10-23 strong
perspective-dev/perspective 1 adequate · 3 strong Rust 360,326 lines 11,341 2026-10-23 strong

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.