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 646 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
nicotine-plus/nicotine-plus 1 adequate · 3 strong Python 72,425 lines 3,141 2026-11-07 strong
inspec/inspec 1 adequate · 3 strong Ruby 166,855 lines 3,100 2026-11-08 strong
influxdata/telegraf 2 adequate · 3 strong Go 731,313 lines 17,880 2026-10-23 strong
ossec/ossec-hids 2 adequate · 3 strong C 255,581 lines 5,070 2026-11-03 strong
sweetalert2/sweetalert2 1 adequate · 3 strong JavaScript 15,921 lines 18,097 2026-10-23 strong
kube-vip/kube-vip 2 adequate · 3 strong Go 60,601 lines 2,996 2026-11-08 strong
victoriametrics/victoriametrics 1 adequate · 4 strong Go 509,859 lines 17,898 2026-10-23 strong
final-form/final-form 1 adequate · 3 strong TypeScript 14,932 lines 3,048 2026-11-07 strong
butterbase-ai/butterbase 1 adequate · 4 strong TypeScript 356,481 lines 3,030 2026-11-07 strong
chdb-io/chdb 1 adequate · 3 strong Python 266,143 lines 2,922 2026-11-08 strong
fetlife/rollout 1 adequate · 3 strong Ruby 6,774 lines 2,904 2026-11-08 strong
padloc/padloc 2 adequate · 3 strong JavaScript 184,127 lines 2,936 2026-11-08 strong
wtfutil/wtf 4 strong Go 47,870 lines 17,129 2026-10-23 strong
apache/apisix 2 adequate · 3 strong Lua 608,990 lines 17,251 2026-10-23 strong
vectifyai/openkb 1 adequate · 3 strong Python 62,199 lines 4,842 2026-11-03 strong
pion/webrtc 4 strong Go 81,527 lines 16,851 2026-10-23 strong
hubotio/hubot 1 adequate · 3 strong JavaScript 11,693 lines 16,801 2026-10-23 strong
sidekiq/sidekiq 2 adequate · 3 strong Ruby 33,591 lines 13,562 2026-10-25 strong
borgbackup/borg 4 strong Python 109,282 lines 13,789 2026-10-25 strong
dokuwiki/dokuwiki 4 strong PHP 263,396 lines 4,734 2026-11-03 strong
akka/akka-core 5 strong Scala 854,694 lines 13,281 2026-10-25 strong
complianceascode/content 2 adequate · 3 strong Shell 692,059 lines 2,833 2026-11-08 strong
kafbat/kafka-ui 5 strong TypeScript 112,603 lines 2,820 2026-11-08 strong
medplum/medplum 2 adequate · 3 strong TypeScript 1,057,184 lines 2,778 2026-11-08 strong
prest/prest 1 adequate · 4 strong Go 73,876 lines 4,630 2026-11-03 strong
apache/doris 2 adequate · 3 strong Java 1,828,323 lines 16,133 2026-10-23 strong
paradedb/paradedb 2 adequate · 3 strong Rust 345,084 lines 9,453 2026-10-28 strong
optimalbits/bull 2 adequate · 3 strong JavaScript 20,676 lines 16,257 2026-10-23 strong
typedb/typedb 2 adequate · 3 strong Rust 191,149 lines 4,500 2026-11-03 strong
flaskbb/flaskbb 1 adequate · 4 strong Python 48,012 lines 2,665 2026-11-08 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.