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 647 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
jabref/jabref 4 strong Java 493,723 lines 4,777 2026-11-07 strong
robusta-dev/krr 2 adequate · 3 strong Python 10,833 lines 4,769 2026-11-07 strong
open-telemetry/opentelemetry-collector 4 strong Go 330,563 lines 7,728 2026-11-03 strong
folke/lazy.nvim 1 adequate · 3 strong Lua 19,093 lines 21,602 2026-10-25 strong
kubeedge/kubeedge 2 adequate · 3 strong Go 317,215 lines 7,621 2026-11-03 strong
matomo-org/matomo 4 strong PHP 1,236,978 lines 21,899 2026-10-25 strong
evcc-io/evcc 2 adequate · 3 strong Go 445,388 lines 7,506 2026-11-03 strong
gitbutlerapp/gitbutler 1 adequate · 3 strong Rust 689,361 lines 21,750 2026-10-25 strong
chroma-core/chroma 2 adequate · 3 strong Rust 519,579 lines 29,554 2026-10-22 strong
nats-io/nats-server 2 adequate · 3 strong Go 475,473 lines 20,797 2026-10-25 strong
scala-js/scala-js 1 adequate · 3 strong Scala 320,692 lines 4,707 2026-11-07 strong
postmanlabs/newman 2 adequate · 3 strong JavaScript 20,998 lines 7,273 2026-11-03 strong
sveltejs/kit 1 adequate · 4 strong JavaScript 143,426 lines 20,831 2026-10-25 strong
browserbase/stagehand 1 adequate · 4 strong TypeScript 312,611 lines 25,793 2026-10-23 strong
mljar/mercury 2 adequate · 3 strong Python 46,033 lines 4,357 2026-11-08 strong
gopasspw/gopass 2 adequate · 3 strong Go 109,465 lines 7,307 2026-11-03 strong
trufflesecurity/trufflehog 2 adequate · 3 strong Go 525,605 lines 28,647 2026-10-22 strong
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
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
gatling/gatling 1 adequate · 3 strong Scala 117,321 lines 6,957 2026-11-03 strong
browser-use/workflow-use 1 adequate · 3 strong Python 36,171 lines 4,244 2026-11-07 strong
uber-go/zap 4 strong Go 26,094 lines 24,677 2026-10-23 strong
thanos-io/thanos 1 adequate · 4 strong Go 287,337 lines 14,258 2026-10-28 strong
nocobase/nocobase 2 adequate · 3 strong TypeScript 2,226,632 lines 24,682 2026-10-23 strong
ppy/osu 4 strong C# 611,156 lines 19,197 2026-10-25 strong
humhub/humhub 1 adequate · 3 strong PHP 397,214 lines 6,775 2026-11-03 strong
bookstackapp/bookstack 2 adequate · 3 strong PHP 285,160 lines 19,056 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.