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 640 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
elementary-data/elementary 1 adequate · 3 strong HTML 65,126 lines 2,429 2026-11-03 strong
measure-sh/measure 2 adequate · 3 strong TypeScript 642,158 lines 1,427 2026-11-08 strong
ovh/utask 2 adequate · 3 strong Go 42,874 lines 1,413 2026-11-08 strong
crev-dev/cargo-crev 4 strong Rust 21,153 lines 2,342 2026-11-03 strong
opendatadiscovery/odd-platform 1 adequate · 3 strong Java 205,132 lines 1,441 2026-11-07 strong
formio/formio 2 adequate · 3 strong JavaScript 119,932 lines 2,328 2026-11-03 strong
lightningnetwork/lnd 2 adequate · 3 strong Go 914,706 lines 8,204 2026-10-23 strong
supabase/storage 1 adequate · 4 strong TypeScript 211,986 lines 1,346 2026-11-08 strong
bentoml/bentoml 2 adequate · 3 strong Python 113,058 lines 8,914 2026-10-22 strong
sequinstream/sequin 1 adequate · 3 strong Elixir 153,757 lines 2,224 2026-11-03 strong
hanami/hanami 1 adequate · 3 strong Ruby 40,626 lines 6,418 2026-10-25 strong
pgbackrest/pgbackrest 1 adequate · 3 strong C 215,770 lines 4,462 2026-10-28 strong
vendurehq/vendure 2 adequate · 3 strong TypeScript 612,894 lines 8,530 2026-10-22 strong
ever-co/ever-traduora 2 adequate · 3 strong JavaScript 69,623 lines 2,139 2026-11-03 strong
freeipa/freeipa 2 adequate · 3 strong Python 678,513 lines 1,298 2026-11-07 strong
drasi-project/drasi-platform 2 adequate · 3 strong C# 124,690 lines 1,256 2026-11-08 strong
fluxcd/flux2 2 adequate · 3 strong Go 67,121 lines 8,458 2026-10-22 strong
livebook-dev/livebook 2 adequate · 3 strong Elixir 124,905 lines 5,872 2026-10-25 strong
onionshare/onionshare 1 adequate · 3 strong Python 56,858 lines 7,184 2026-10-23 strong
rstudio/shiny 1 adequate · 3 strong R 151,600 lines 5,695 2026-10-25 strong
firebase/firebase-ios-sdk 1 adequate · 3 strong C++ 816,312 lines 6,980 2026-10-23 strong
dolibarr/dolibarr 2 adequate · 3 strong PHP 1,516,686 lines 7,761 2026-10-22 strong
scality/cloudserver 2 adequate · 3 strong JavaScript 206,787 lines 1,954 2026-11-03 strong
luraproject/lura 1 adequate · 4 strong Go 23,265 lines 6,805 2026-10-23 strong
bugbakery/audapolis 1 adequate · 4 strong TypeScript 16,774 lines 1,905 2026-11-03 strong
grpc-ecosystem/go-grpc-middleware 4 strong Go 14,363 lines 6,759 2026-10-23 strong
kptdev/kpt 1 adequate · 4 strong Go 125,440 lines 1,900 2026-11-03 strong
tanstack/form 4 strong TypeScript 123,755 lines 6,742 2026-10-23 strong
unkeyed/unkey 2 adequate · 3 strong Go 743,381 lines 5,455 2026-10-25 strong
tautulli/tautulli 2 adequate · 3 strong Python 639,556 lines 6,618 2026-10-23 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.