Rust repositories

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 121 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
zensical/zensical 2 adequate · 3 strong Rust 100,183 lines 6,071 2026-11-03 strong
scanopy/scanopy 4 adequate · 1 strong Rust 665,851 lines 5,932 2026-11-03 adequate
neondatabase/neon 2 adequate · 3 strong Rust 457,599 lines 23,246 2026-10-22 strong
agentgateway/agentgateway 2 adequate · 3 strong Rust 592,107 lines 5,907 2026-11-03 strong
pgdogdev/pgdog 2 adequate · 3 strong Rust 227,298 lines 5,594 2026-11-03 adequate
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
arroyosystems/arroyo 3 adequate · 2 strong Rust 142,558 lines 5,077 2026-11-03 adequate
asciinema/asciinema 1 adequate · 2 strong Rust 11,754 lines 17,905 2026-10-23 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
memvid/memvid 2 adequate · 3 strong Rust 78,353 lines 16,608 2026-10-23 strong
paradedb/paradedb 2 adequate · 3 strong Rust 345,084 lines 9,453 2026-10-28 strong
quickwit-oss/tantivy 1 adequate · 2 strong Rust 187,819 lines 16,253 2026-10-23 adequate
typedb/typedb 2 adequate · 3 strong Rust 191,149 lines 4,500 2026-11-03 strong
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
deeplethe/utopia 2 adequate · 3 strong Rust 366,732 lines 8,581 2026-10-28 strong
serde-rs/serde 1 adequate · 2 strong Rust 43,784 lines 10,831 2026-10-25 adequate
dbt-labs/dbt 1 adequate · 3 strong Rust 930,336 lines 14,063 2026-10-22 strong
lance-format/lance 1 adequate · 3 strong Rust 1,273,332 lines 7,224 2026-10-28 strong
rustic-rs/rustic 4 adequate · 1 strong Rust 18,707 lines 3,364 2026-11-03 adequate
lancedb/lancedb 1 adequate · 4 strong Rust 307,285 lines 11,754 2026-10-23 strong
eclipse-zenoh/zenoh 1 adequate · 2 strong Rust 224,709 lines 3,317 2026-11-03 adequate
cocoindex-io/cocoindex 4 strong Rust 247,382 lines 11,745 2026-10-23 strong
perspective-dev/perspective 1 adequate · 3 strong Rust 360,326 lines 11,341 2026-10-23 strong
quickwit-oss/quickwit 4 adequate · 1 strong Rust 347,070 lines 11,735 2026-10-22 adequate
moltis-org/moltis 2 adequate · 2 strong Rust 803,386 lines 2,939 2026-11-03 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

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.