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
django-oscar/django-oscar 4 strong Python 94,057 lines 6,627 2026-10-23 strong
cloudquery/cloudquery 1 adequate · 4 strong Go 163,747 lines 6,544 2026-10-23 strong
decidim/decidim 1 adequate · 4 strong Ruby 907,688 lines 1,846 2026-11-03 strong
codeberg.org/readeck/readeck 2 adequate · 3 strong Go 179,340 lines 1,191 2026-11-07 strong
roxy-wi/roxy-wi 2 adequate · 3 strong Python 178,738 lines 1,833 2026-11-03 strong
dbt-labs/metricflow 2 adequate · 3 strong Python 1,022,841 lines 1,857 2026-11-03 strong
part-db/part-db-server 2 adequate · 3 strong PHP 204,138 lines 1,826 2026-11-03 strong
passbolt/passbolt_api 2 adequate · 3 strong PHP 481,336 lines 6,185 2026-10-23 strong
flectar/mail 1 adequate · 3 strong Rust 320,029 lines 1,745 2026-11-03 strong
spatie/laravel-backup 4 strong PHP 13,692 lines 6,026 2026-10-23 strong
lobsters/lobsters 2 adequate · 3 strong Ruby 31,848 lines 4,845 2026-10-25 strong
fluxml/flux.jl 1 adequate · 3 strong Julia 26,029 lines 4,751 2026-10-25 strong
kgateway-dev/kgateway 2 adequate · 3 strong Go 467,140 lines 5,723 2026-10-23 strong
sqlmesh/sqlmesh 2 adequate · 3 strong Python 338,931 lines 3,335 2026-10-28 strong
peerdb-io/peerdb 2 adequate · 3 strong Go 197,242 lines 3,310 2026-10-28 strong
influxdata/chronograf 2 adequate · 3 strong TypeScript 254,649 lines 1,568 2026-11-03 strong
jaegertracing/jaeger-ui 4 strong TypeScript 151,418 lines 1,544 2026-11-03 strong
growilabs/growi 2 adequate · 3 strong TypeScript 657,399 lines 1,476 2026-11-03 strong
edgenesis/shifu 2 adequate · 3 strong Go 41,636 lines 1,436 2026-11-03 strong
zenml-io/zenml 1 adequate · 4 strong Python 597,046 lines 5,624 2026-10-22 strong
pomerium/pomerium 2 adequate · 3 strong Go 329,649 lines 5,064 2026-10-23 strong
clidey/whodb 2 adequate · 3 strong Go 464,188 lines 5,041 2026-10-23 strong
cloudera/hue 1 adequate · 3 strong JavaScript 1,530,482 lines 1,410 2026-11-03 strong
surveyjs/survey-library 1 adequate · 3 strong TypeScript 534,480 lines 4,913 2026-10-23 strong
formkit/formkit 1 adequate · 3 strong TypeScript 102,743 lines 4,779 2026-10-23 strong
jenkins-x/jx 2 adequate · 3 strong Go 7,014 lines 4,691 2026-10-23 strong
acinq/eclair 1 adequate · 4 strong Scala 169,740 lines 1,349 2026-11-03 strong
gitlab.com/cryptsetup/cryptsetup 4 strong — 100,666 lines 851 2026-11-07 strong
enterpilot/gomodel 2 adequate · 3 strong Go 550,673 lines 1,298 2026-11-03 strong
emissary-ingress/emissary 2 adequate · 3 strong Python 201,565 lines 4,521 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.