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 645 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
mosn/mosn 1 adequate · 4 strong Go 266,382 lines 4,507 2026-11-03 strong
playframework/playframework 2 adequate · 3 strong Scala 265,998 lines 12,615 2026-10-25 strong
aboutcode-org/scancode-toolkit 1 adequate · 3 strong Python 1,825,394 lines 2,662 2026-11-08 strong
rubocop/rubocop 4 strong Ruby 406,900 lines 12,908 2026-10-25 strong
crate/crate 4 strong Java 858,205 lines 4,450 2026-11-03 strong
crunchydata/postgres-operator 2 adequate · 3 strong Go 124,157 lines 4,456 2026-11-03 strong
cilium/hubble 1 adequate · 3 strong Makefile 21,926 lines 4,376 2026-11-03 strong
dependencytrack/dependency-track 1 adequate · 4 strong Java 412,000 lines 4,401 2026-11-03 strong
heyform/heyform 2 adequate · 3 strong TypeScript 129,387 lines 9,055 2026-10-28 strong
openflagr/flagr 2 adequate · 3 strong Go 70,879 lines 2,611 2026-11-08 strong
algorithmicsuperintelligence/optillm 2 adequate · 3 strong Python 57,794 lines 4,335 2026-11-03 strong
kludex/starlette 4 strong Python 28,883 lines 12,640 2026-10-25 strong
swanhubx/swanlab 4 strong Python 75,429 lines 4,350 2026-11-03 strong
altinity/clickhouse-operator 2 adequate · 3 strong Go 533,997 lines 2,578 2026-11-08 strong
oauth2-proxy/oauth2-proxy 2 adequate · 3 strong Go 105,439 lines 15,241 2026-10-23 strong
wal-g/wal-g 2 adequate · 3 strong Go 161,733 lines 4,326 2026-11-03 strong
elastic/logstash 2 adequate · 3 strong Java 227,604 lines 14,965 2026-10-23 strong
deeplethe/utopia 2 adequate · 3 strong Rust 366,732 lines 8,581 2026-10-28 strong
sodadata/soda-core 1 adequate · 4 strong Python 103,426 lines 2,463 2026-11-08 strong
ankidroid/anki-android 1 adequate · 3 strong Kotlin 246,887 lines 11,889 2026-10-25 strong
tonejs/tone.js 1 adequate · 3 strong TypeScript 67,786 lines 14,787 2026-10-23 strong
esphome/esphome 2 adequate · 3 strong C++ 857,176 lines 11,722 2026-10-25 strong
griddb/griddb 2 adequate · 3 strong C++ 988,535 lines 2,473 2026-11-07 strong
rotki/rotki 2 adequate · 3 strong Python 1,121,031 lines 4,073 2026-11-03 strong
kopia/kopia 1 adequate · 3 strong Go 173,900 lines 14,410 2026-10-23 strong
element-hq/element-x-android 4 strong Kotlin 408,128 lines 2,424 2026-11-08 strong
ravendb/ravendb 2 adequate · 3 strong C# 1,948,386 lines 4,014 2026-11-03 strong
nanobrowser/nanobrowser 1 adequate · 3 strong TypeScript 82,608 lines 14,163 2026-10-23 strong
documize/community 2 adequate · 3 strong JavaScript 201,640 lines 2,425 2026-11-07 strong
automatisch/automatisch 2 adequate · 3 strong JavaScript 152,769 lines 14,000 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.