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 1,001 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
files-community/files 2 adequate · 2 strong C# 151,968 lines 45,663 2026-10-25 adequate
sharkdp/fd 2 strong Rust 11,649 lines 44,614 2026-10-25 adequate
ansible/awx 3 adequate · 1 strong Python 223,387 lines 15,618 2026-11-03 adequate
owasp-amass/amass 5 adequate Go 39,830 lines 15,457 2026-11-03 adequate
coaidev/coai 4 adequate · 1 strong TypeScript 68,084 lines 9,334 2026-11-07 adequate
firezone/firezone 3 adequate · 2 strong Elixir 506,227 lines 9,105 2026-11-08 adequate
teslamate-org/teslamate 2 adequate · 3 strong Elixir 179,834 lines 9,065 2026-11-08 adequate
sxyazi/yazi 2 adequate · 1 strong Rust 91,229 lines 42,508 2026-10-25 adequate
exelban/stats 3 adequate · 1 strong Swift 49,507 lines 42,213 2026-10-25 adequate
mage-ai/mage-ai 4 adequate · 1 strong Python 551,181 lines 8,836 2026-11-08 adequate
owncloud/core 2 adequate · 2 strong PHP 851,988 lines 8,839 2026-11-07 adequate
labring/fastgpt 3 adequate · 2 strong TypeScript 997,571 lines 29,931 2026-10-28 adequate
vim/vim 3 adequate · 1 strong Vim Script 1,436,725 lines 41,005 2026-10-25 adequate
teamwiseflow/xiaobei 4 adequate · 1 strong Python 130,977 lines 8,684 2026-11-08 adequate
rikkahub/rikkahub 3 adequate · 2 strong Kotlin 257,729 lines 8,695 2026-11-07 adequate
duckdb/duckdb 1 adequate · 2 strong C++ 1,070,858 lines 41,709 2026-10-25 adequate
the-pr-agent/pr-agent 3 adequate · 2 strong Python 224,506 lines 14,267 2026-11-03 adequate
schollz/croc 3 adequate · 2 strong Go 83,381 lines 40,474 2026-10-25 adequate
growthbook/growthbook 4 adequate · 1 strong TypeScript 1,185,125 lines 8,526 2026-11-07 adequate
safing/portmaster 4 adequate · 1 strong Go 208,941 lines 14,019 2026-11-03 adequate
qbittorrent/qbittorrent 3 adequate · 1 strong C++ 209,125 lines 40,459 2026-10-25 adequate
lapce/lapce 2 adequate · 2 strong Rust 74,599 lines 38,868 2026-10-25 adequate
dnscrypt/dnscrypt-proxy 4 adequate · 1 strong Go 24,544 lines 13,808 2026-11-03 adequate
automazeio/ccpm 1 adequate · 1 strong Shell 2,970 lines 8,412 2026-11-07 adequate
koalaman/shellcheck 1 adequate · 2 strong Haskell 23,599 lines 40,090 2026-10-25 adequate
bloopai/vibe-kanban 3 adequate · 2 strong Rust 276,167 lines 28,484 2026-10-28 adequate
directus/directus 3 adequate · 2 strong TypeScript 689,516 lines 38,722 2026-10-25 adequate
keygraphhq/shannon 4 adequate · 1 strong TypeScript 66,267 lines 49,255 2026-10-23 adequate
teamnewpipe/newpipe 3 adequate · 1 strong Java 134,421 lines 39,825 2026-10-25 adequate
nextauthjs/next-auth 3 adequate · 2 strong TypeScript 64,348 lines 28,373 2026-10-28 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.