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
nsqio/nsq 3 adequate · 2 strong Go 26,831 lines 25,771 2026-10-23 adequate
streetwriters/notesnook 3 adequate · 1 strong TypeScript 300,203 lines 14,845 2026-10-28 adequate
opensignlabs/opensign 5 adequate JavaScript 92,324 lines 7,215 2026-11-03 adequate
cilium/cilium 3 adequate · 2 strong Go 1,479,547 lines 25,711 2026-10-23 adequate
wagtail/wagtail 2 adequate · 3 strong Python 419,102 lines 20,507 2026-10-25 strong
open-multi-agent/open-multi-agent 4 strong TypeScript 154,895 lines 7,044 2026-11-03 strong
crystal-lang/crystal 1 adequate · 3 strong Crystal 566,081 lines 20,436 2026-10-25 strong
budibase/budibase 4 adequate · 1 strong TypeScript 684,867 lines 28,342 2026-10-22 adequate
onlyoffice/documentserver 3 adequate Shell 10,879 lines 7,082 2026-11-03 adequate
vespa-engine/vespa 3 adequate · 2 strong Java 2,031,838 lines 7,158 2026-11-03 adequate
linkwarden/linkwarden 4 adequate · 1 strong TypeScript 77,398 lines 19,845 2026-10-25 adequate
activepieces/activepieces 4 adequate · 1 strong TypeScript 2,038,668 lines 25,189 2026-10-23 adequate
katanemo/plano 3 adequate · 2 strong Rust 103,798 lines 7,107 2026-11-03 adequate
taosdata/tdengine 2 adequate · 3 strong C 1,958,618 lines 25,169 2026-10-23 strong
bitwarden/server 1 adequate · 4 strong C# 1,994,868 lines 20,202 2026-10-25 strong
tj/n 2 strong Shell 2,747 lines 19,510 2026-10-25 adequate
haproxy/haproxy 3 adequate · 1 strong C 516,419 lines 6,968 2026-11-03 adequate
gatling/gatling 1 adequate · 3 strong Scala 117,321 lines 6,957 2026-11-03 strong
apache/skywalking 3 adequate · 2 strong Java 592,977 lines 24,975 2026-10-23 adequate
uber-go/zap 4 strong Go 26,094 lines 24,677 2026-10-23 strong
komari-monitor/komari 2 adequate · 3 strong Go 83,108 lines 6,882 2026-11-03 strong
clearml/clearml 2 adequate · 2 strong Python 262,814 lines 6,928 2026-11-03 adequate
thanos-io/thanos 1 adequate · 4 strong Go 287,337 lines 14,258 2026-10-28 strong
dataease/dataease 5 adequate Java 514,668 lines 24,626 2026-10-23 adequate
nocobase/nocobase 2 adequate · 3 strong TypeScript 2,226,632 lines 24,682 2026-10-23 strong
infobyte/faraday 3 adequate · 2 strong Python 90,000 lines 6,838 2026-11-03 adequate
hashicorp/vagrant 3 strong Ruby 165,793 lines 27,216 2026-10-22 adequate
simplex-chat/simplex-chat 4 adequate · 1 strong Haskell 454,035 lines 19,504 2026-10-25 adequate
typesense/typesense 2 adequate · 3 strong C++ 289,731 lines 27,026 2026-10-22 strong
postgresml/postgresml 4 adequate · 1 strong Rust 96,274 lines 6,826 2026-11-03 adequate

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.