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 647 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
tribler/tribler 2 adequate · 3 strong Python 47,827 lines 5,343 2026-11-08 strong
shlinkio/shlink 1 adequate · 4 strong PHP 60,031 lines 5,401 2026-11-08 strong
codenotary/immudb 2 adequate · 3 strong Go 270,603 lines 9,049 2026-11-03 strong
fluxcd/flagger 1 adequate · 4 strong Go 110,118 lines 5,421 2026-11-08 strong
delta-io/delta 2 adequate · 3 strong Scala 697,961 lines 9,066 2026-11-03 strong
karatelabs/karate 4 strong Java 282,781 lines 9,003 2026-11-03 strong
lukevella/rallly 2 adequate · 3 strong TypeScript 170,650 lines 5,275 2026-11-08 strong
mjmlio/mjml 1 adequate · 3 strong JavaScript 18,845 lines 18,284 2026-10-28 strong
tsuru/tsuru 2 adequate · 3 strong Go 177,936 lines 5,326 2026-11-08 strong
composiohq/composio 2 adequate · 3 strong TypeScript 500,218 lines 30,941 2026-10-23 strong
navidrome/navidrome 2 adequate · 3 strong Go 322,101 lines 23,847 2026-10-25 strong
statelyai/xstate 1 adequate · 3 strong TypeScript 122,357 lines 30,348 2026-10-23 strong
getanteon/anteon 2 adequate · 3 strong Go 25,709 lines 8,514 2026-11-03 strong
better-auth/better-auth 2 adequate · 3 strong TypeScript 527,560 lines 30,440 2026-10-23 strong
pycqa/bandit 1 adequate · 3 strong Python 27,519 lines 8,369 2026-11-03 strong
wukongim/wukongim 2 adequate · 3 strong Go 1,940,751 lines 4,986 2026-11-08 strong
basecamp/fizzy 1 adequate · 4 strong Ruby 83,269 lines 8,282 2026-11-03 strong
suitenumerique/docs 1 adequate · 4 strong Python 177,768 lines 16,953 2026-10-28 strong
prefecthq/prefect 2 adequate · 3 strong Python 946,356 lines 23,936 2026-10-25 strong
cockroachdb/cockroach 2 adequate · 3 strong Go 2,370,315 lines 32,606 2026-10-22 strong
tutao/tutanota 1 adequate · 3 strong TypeScript 794,648 lines 8,105 2026-11-03 strong
statamic/cms 1 adequate · 3 strong PHP 547,436 lines 4,903 2026-11-08 strong
reflex-dev/reflex 2 adequate · 3 strong Python 467,491 lines 28,977 2026-10-23 strong
repowise-dev/repowise 2 adequate · 3 strong Python 1,688,885 lines 8,120 2026-11-03 strong
hledgerorg/hledger 2 adequate · 3 strong Haskell 140,439 lines 4,810 2026-11-08 strong
ottermind/chat2db 2 adequate · 3 strong Java 505,964 lines 28,331 2026-10-23 strong
grafana/k6 5 strong Go 275,771 lines 32,010 2026-10-22 strong
steel-dev/steel-browser 2 adequate · 3 strong TypeScript 54,989 lines 7,916 2026-11-03 strong
werf/werf 2 adequate · 3 strong Go 202,006 lines 4,738 2026-11-08 strong
jabref/jabref 4 strong Java 493,723 lines 4,777 2026-11-07 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.