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
lancedb/lancedb 1 adequate · 4 strong Rust 307,285 lines 11,754 2026-10-23 strong
owncast/owncast 1 adequate · 4 strong Go 192,134 lines 11,624 2026-10-23 strong
major/mysqltuner-perl 1 adequate · 3 strong Perl 46,405 lines 9,480 2026-10-25 strong
kanaries/graphic-walker 1 adequate · 3 strong TypeScript 57,148 lines 3,286 2026-11-03 strong
storj/storj 2 adequate · 3 strong Go 834,667 lines 3,284 2026-11-03 strong
vouch/vouch-proxy 1 adequate · 4 strong Go 9,985 lines 3,281 2026-11-03 strong
octoprint/octoprint 1 adequate · 3 strong Python 225,605 lines 9,117 2026-10-25 strong
open-mercato/open-mercato 2 adequate · 3 strong TypeScript 1,802,973 lines 1,881 2026-11-08 strong
heavyai/heavydb 2 adequate · 3 strong C++ 869,449 lines 3,120 2026-11-03 strong
kedro-org/kedro 1 adequate · 4 strong Python 91,632 lines 11,031 2026-10-23 strong
hapifhir/hapi-fhir 1 adequate · 3 strong Java 1,853,437 lines 2,427 2026-11-05 strong
dtm-labs/dtm 2 adequate · 3 strong Go 21,491 lines 10,923 2026-10-23 strong
crossplane/crossplane 1 adequate · 4 strong Go 177,826 lines 12,189 2026-10-22 strong
skypilot-org/skypilot 2 adequate · 3 strong Python 724,101 lines 10,738 2026-10-23 strong
django-cms/django-cms 1 adequate · 3 strong Python 132,493 lines 10,679 2026-10-23 strong
kedacore/keda 1 adequate · 4 strong Go 217,273 lines 10,657 2026-10-23 strong
avo-hq/avo 2 adequate · 3 strong Ruby 100,302 lines 1,812 2026-11-08 strong
mautic/mautic 2 adequate · 3 strong PHP 701,569 lines 10,830 2026-10-23 strong
root-gg/plik 2 adequate · 3 strong Go 92,728 lines 1,839 2026-11-07 strong
sveltia/sveltia-cms 1 adequate · 3 strong JavaScript 637,043 lines 3,034 2026-11-03 strong
fwdcloudsec/granted 1 adequate · 3 strong Go 16,642 lines 1,810 2026-11-07 strong
graylog2/graylog2-server 2 adequate · 3 strong Java 1,250,523 lines 8,151 2026-10-25 strong
lf-edge/ekuiper 2 adequate · 3 strong Go 305,770 lines 1,747 2026-11-08 strong
polarsource/polar 2 adequate · 3 strong Python 1,144,782 lines 10,411 2026-10-23 strong
dograh-hq/dograh 2 adequate · 3 strong Python 356,854 lines 5,972 2026-10-28 strong
dataplat/dbatools 4 strong PowerShell 376,142 lines 2,858 2026-11-03 strong
wandb/wandb 1 adequate · 4 strong Python 427,201 lines 11,308 2026-10-22 strong
kube-logging/logging-operator 2 adequate · 3 strong Go 192,507 lines 1,716 2026-11-08 strong
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

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.