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
partykit/partykit 1 adequate · 3 strong TypeScript 50,023 lines 5,744 2026-11-03 strong
bettercap/bettercap 4 adequate · 1 strong Go 112,414 lines 20,181 2026-10-23 adequate
apache/casbin 1 adequate · 3 strong Go 80,755 lines 20,467 2026-10-23 strong
gotify/server 2 adequate · 3 strong Go 29,734 lines 15,991 2026-10-25 strong
superstreamlabs/memphis 1 adequate · 4 strong Go 356,809 lines 3,444 2026-11-08 strong
mikefarah/yq 1 adequate · 3 strong Go 66,439 lines 16,017 2026-10-25 strong
signalapp/signal-desktop 2 adequate · 2 strong TypeScript 1,151,574 lines 16,556 2026-10-25 adequate
pgdogdev/pgdog 2 adequate · 3 strong Rust 227,298 lines 5,594 2026-11-03 adequate
zaproxy/zaproxy 1 adequate · 3 strong Java 348,209 lines 15,836 2026-10-25 strong
flow-launcher/flow.launcher 2 adequate · 2 strong C# 82,970 lines 15,698 2026-10-25 adequate
linkerd/linkerd2 2 adequate · 3 strong Go 285,803 lines 11,521 2026-10-28 strong
airbytehq/airbyte 3 adequate · 2 strong Python 1,007,689 lines 22,254 2026-10-22 adequate
jackett/jackett 1 adequate · 3 strong C# 168,287 lines 16,089 2026-10-25 strong
spree/spree 1 adequate · 3 strong Ruby 712,132 lines 15,735 2026-10-25 strong
openemr/openemr 4 adequate · 1 strong PHP 1,735,504 lines 5,570 2026-11-03 adequate
permitio/opal 3 adequate · 2 strong Python 67,114 lines 5,524 2026-11-03 adequate
3proxy/3proxy 2 adequate · 1 strong C 47,961 lines 5,572 2026-11-03 adequate
apache/gravitino 1 adequate · 4 strong Java 1,399,544 lines 3,344 2026-11-07 strong
uvdesk/community-skeleton 2 adequate CSS 24,666 lines 19,640 2026-10-23 adequate
eclipse-zenoh/zenoh 1 adequate · 2 strong Rust 224,709 lines 3,317 2026-11-07 adequate
gitlab.com/calcprogrammer1/openrgb 3 adequate · 2 strong — 496,970 lines 3,505 2026-11-07 adequate
activitywatch/activitywatch 4 adequate Python 18,235 lines 19,357 2026-10-23 adequate
avaiga/taipy 1 adequate · 4 strong Python 173,217 lines 19,445 2026-10-23 strong
encode/httpx 1 adequate · 3 strong Python 33,284 lines 15,515 2026-10-25 strong
decaporg/decap-cms 2 adequate · 3 strong JavaScript 304,253 lines 19,441 2026-10-23 strong
shlinkio/shlink 1 adequate · 4 strong PHP 60,031 lines 5,401 2026-11-03 strong
vitessio/vitess 3 adequate · 2 strong Go 1,681,787 lines 21,390 2026-10-22 adequate
tribler/tribler 2 adequate · 3 strong Python 47,827 lines 5,343 2026-11-03 strong
worklenz/worklenz 3 adequate · 2 strong TypeScript 825,246 lines 3,280 2026-11-07 adequate
enterprisedb/barman 1 adequate · 3 strong Python 138,467 lines 3,272 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.