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
rustdesk/rustdesk 2 adequate · 3 strong Rust 295,034 lines 124,631 2026-10-25 strong
spacedriveapp/spacedrive 3 adequate · 1 strong Rust 445,606 lines 39,398 2026-11-03 adequate
tauri-apps/tauri 2 adequate · 3 strong Rust 172,589 lines 111,445 2026-10-25 strong
zama-ai/fhevm 2 adequate · 3 strong Rust 1,432,282 lines 24,744 2026-11-07 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
ccusage/ccusage 1 adequate · 2 strong Rust 97,153 lines 19,353 2026-11-07 adequate
kitao/pyxel 3 adequate · 1 strong Rust 61,851 lines 18,557 2026-11-07 adequate
eythaann/seelen-ui 3 adequate · 1 strong Rust 176,254 lines 18,363 2026-11-07 adequate
clap-rs/clap 3 strong Rust 103,662 lines 16,937 2026-11-07 adequate
tursodatabase/turso 1 adequate · 3 strong Rust 1,056,899 lines 25,131 2026-11-03 strong
rtk-ai/rtk 2 adequate · 2 strong Rust 258,487 lines 84,376 2026-10-23 adequate
burntsushi/ripgrep 3 strong Rust 66,552 lines 68,602 2026-10-25 adequate
dani-garcia/vaultwarden 2 adequate · 2 strong Rust 66,596 lines 68,218 2026-10-25 adequate
alacritty/alacritty 2 adequate · 2 strong Rust 38,433 lines 65,834 2026-10-25 adequate
sharkdp/bat 4 adequate Rust 75,936 lines 60,575 2026-10-25 adequate
meilisearch/meilisearch 2 adequate · 3 strong Rust 285,291 lines 59,414 2026-10-25 adequate
starship/starship 1 adequate · 3 strong Rust 230,693 lines 60,082 2026-10-25 strong
astral-sh/ruff 4 adequate · 1 strong Rust 1,284,076 lines 49,818 2026-10-25 adequate
helix-editor/helix 1 adequate · 2 strong Rust 412,377 lines 46,361 2026-10-25 adequate
aaif-goose/goose 2 adequate · 3 strong Rust 610,585 lines 55,587 2026-10-23 strong
sharkdp/fd 2 strong Rust 11,649 lines 44,614 2026-10-25 adequate
sxyazi/yazi 2 adequate · 1 strong Rust 91,229 lines 42,508 2026-10-25 adequate
lapce/lapce 2 adequate · 2 strong Rust 74,599 lines 38,868 2026-10-25 adequate
nushell/nushell 1 adequate · 3 strong Rust 482,405 lines 40,580 2026-10-25 strong
ajeetdsouza/zoxide 2 strong Rust 7,656 lines 39,711 2026-10-25 adequate
bloopai/vibe-kanban 3 adequate · 2 strong Rust 276,167 lines 28,484 2026-10-28 adequate
run-llama/liteparse 4 adequate · 1 strong Rust 85,613 lines 12,975 2026-11-03 adequate
herdrdev/herdr 3 strong Rust 387,249 lines 45,521 2026-10-23 adequate
juspay/hyperswitch 4 adequate · 1 strong Rust 1,795,493 lines 45,400 2026-10-23 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.