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 642 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
fossbilling/fossbilling 2 adequate · 3 strong PHP 231,595 lines 1,721 2026-11-07 strong
typelevel/skunk 1 adequate · 4 strong Scala 32,054 lines 1,667 2026-11-08 strong
hyperdxio/hyperdx 2 adequate · 3 strong TypeScript 585,897 lines 9,963 2026-10-23 strong
dbos-inc/dbos-transact-py 4 strong Python 79,825 lines 1,653 2026-11-08 strong
puma/puma 1 adequate · 3 strong Ruby 42,714 lines 7,917 2026-10-25 strong
masstransit/masstransit 4 strong C# 434,520 lines 7,802 2026-10-25 strong
supabase/realtime 2 adequate · 3 strong Elixir 116,133 lines 7,644 2026-10-25 strong
xonsh/xonsh 4 strong Python 130,236 lines 9,685 2026-10-23 strong
krakend/krakend-ce 2 adequate · 3 strong Go 5,635 lines 2,702 2026-11-03 strong
goplus/xgo 1 adequate · 3 strong Go 89,812 lines 9,487 2026-10-23 strong
open-web-analytics/open-web-analytics 4 strong PHP 219,212 lines 2,697 2026-11-03 strong
linuxserver/heimdall 1 adequate · 4 strong PHP 61,924 lines 9,365 2026-10-23 strong
absmach/magistrala 2 adequate · 3 strong Go 119,482 lines 2,658 2026-11-03 strong
duendesoftware/products 2 adequate · 3 strong C# 520,009 lines 1,613 2026-11-07 strong
bitnami/sealed-secrets 2 adequate · 3 strong Go 25,226 lines 9,316 2026-10-23 strong
gridstack/gridstack.js 1 adequate · 3 strong TypeScript 57,325 lines 9,208 2026-10-23 strong
prestashop/prestashop 1 adequate · 4 strong PHP 1,368,776 lines 9,234 2026-10-23 strong
supabase/auth 5 strong Go 116,528 lines 2,592 2026-11-03 strong
allegro/ralph 2 adequate · 3 strong Python 106,444 lines 2,532 2026-11-03 strong
pixelfed/pixelfed 2 adequate · 3 strong PHP 363,724 lines 7,116 2026-10-25 strong
inkeep/agents 2 adequate · 3 strong TypeScript 944,577 lines 1,489 2026-11-08 strong
idurar/idurar-erp-crm 2 adequate · 3 strong JavaScript 25,926 lines 8,909 2026-10-23 strong
builderio/builder 1 adequate · 3 strong TypeScript 11,872 lines 8,870 2026-10-23 strong
frappe/builder 2 adequate · 3 strong Python 89,840 lines 2,464 2026-11-03 strong
threemammals/ocelot 2 adequate · 3 strong C# 82,725 lines 8,717 2026-10-23 strong
exceptionless/exceptionless 1 adequate · 4 strong C# 301,673 lines 2,456 2026-11-03 strong
prometheus/alertmanager 1 adequate · 4 strong Go 119,424 lines 8,669 2026-10-23 strong
sylius/sylius 2 adequate · 3 strong PHP 622,568 lines 8,562 2026-10-23 strong
nager/nager.date 1 adequate · 3 strong C# 48,408 lines 1,439 2026-11-08 strong
processone/ejabberd 1 adequate · 3 strong Erlang 179,463 lines 6,734 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.