The library

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,656 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
getzola/zola 2 adequate · 2 strong Rust 43,441 lines 17,550 2026-10-23 adequate
effect-ts/effect 1 adequate · 3 strong TypeScript 976,477 lines 17,365 2026-10-23 strong
kotlin/kotlinx.coroutines 1 adequate · 2 strong Kotlin 133,771 lines 13,816 2026-10-25 adequate
padloc/padloc 2 adequate · 3 strong JavaScript 184,127 lines 2,936 2026-11-08 strong
wazuh/wazuh 3 adequate · 2 strong C++ 1,868,854 lines 17,378 2026-10-23 adequate
kubesphere/kubesphere 4 adequate · 1 strong Go 224,690 lines 17,066 2026-10-23 adequate
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
seldonio/seldon-core 3 adequate · 2 strong Go 322,460 lines 4,784 2026-11-03 adequate
integuru-ai/integuru 1 adequate · 1 strong Python 2,441 lines 4,790 2026-11-03 adequate
pion/webrtc 4 strong Go 81,527 lines 16,851 2026-10-23 strong
thunderbird/thunderbird-android 2 adequate · 2 strong Kotlin 392,465 lines 14,038 2026-10-25 adequate
hledgerorg/hledger 2 adequate · 3 strong Haskell 140,439 lines 4,810 2026-11-03 strong
inkeep/open-knowledge 3 adequate · 1 strong TypeScript 1,718,706 lines 4,776 2026-11-03 adequate
argoproj/argo-workflows 4 adequate · 1 strong Go 415,344 lines 17,050 2026-10-23 adequate
hubotio/hubot 1 adequate · 3 strong JavaScript 11,693 lines 16,801 2026-10-23 strong
infiniflow/infinity 3 adequate · 2 strong C++ 674,232 lines 4,756 2026-11-03 adequate
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
openimsdk/open-im-server 4 adequate · 1 strong Go 80,175 lines 16,721 2026-10-23 adequate
mealie-recipes/mealie 3 adequate · 2 strong Python 330,864 lines 13,342 2026-10-25 adequate
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
apache/seatunnel 3 adequate · 2 strong Java 1,468,875 lines 9,767 2026-10-28 adequate
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
memgraph/memgraph 4 adequate · 1 strong C++ 926,307 lines 4,643 2026-11-03 adequate
winsiderss/systeminformer 2 adequate · 2 strong C 1,564,958 lines 16,315 2026-10-23 adequate
wallabag/wallabag 2 adequate · 3 strong PHP 83,995 lines 12,989 2026-10-25 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.