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 641 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
emissary-ingress/emissary 2 adequate · 3 strong Python 201,565 lines 4,521 2026-10-23 strong
elastic/apm-server 5 strong Go 114,220 lines 1,271 2026-11-03 strong
archtechx/tenancy 2 adequate · 3 strong PHP 34,010 lines 4,425 2026-10-23 strong
lunarphp/lunar 1 adequate · 3 strong PHP 145,979 lines 3,763 2026-10-23 strong
owncloud/ocis 2 adequate · 3 strong Go 652,310 lines 2,171 2026-10-28 strong
nextflow-io/nextflow 1 adequate · 3 strong Groovy 690,031 lines 3,516 2026-10-23 strong
shopware/shopware 5 strong PHP 2,123,507 lines 3,454 2026-10-23 strong
terminusdb/terminusdb 2 adequate · 3 strong Prolog 182,550 lines 3,456 2026-10-23 strong
maplibre/maplibre-compose 1 adequate · 3 strong Kotlin 177,265 lines 585 2026-11-08 strong
deepfence/secretscanner 1 adequate · 3 strong Go 2,911 lines 3,401 2026-10-23 strong
celery/kombu 4 strong Python 63,448 lines 3,151 2026-10-23 strong
gitlab.com/gitlab-org/gitlab-runner 2 adequate · 3 strong — 348,703 lines 2,570 2026-10-25 strong
oauthlib/oauthlib 1 adequate · 3 strong Python 24,733 lines 2,988 2026-10-23 strong
zenstackhq/zenstack 4 strong TypeScript 218,120 lines 2,955 2026-10-23 strong
jitsi/jitsi-meet-electron 1 adequate · 3 strong TypeScript 6,459 lines 1,635 2026-10-28 strong
wpengine/faustjs 2 adequate · 3 strong TypeScript 41,260 lines 1,608 2026-10-28 strong
datazip-inc/olake 2 adequate · 3 strong Go 129,636 lines 1,571 2026-10-28 strong
fsprojects/paket 1 adequate · 3 strong F# 97,083 lines 2,086 2026-10-25 strong
pac4j/pac4j 1 adequate · 3 strong Java 117,467 lines 2,537 2026-10-23 strong
getsentry/relay 2 adequate · 3 strong Rust 282,085 lines 401 2026-11-08 strong
victoriametrics/victorialogs 2 adequate · 3 strong Go 252,099 lines 2,399 2026-10-23 strong
meltano/meltano 1 adequate · 3 strong Python 146,467 lines 2,667 2026-10-22 strong
kubernetes-sigs/aws-iam-authenticator 2 adequate · 3 strong Go 19,135 lines 2,338 2026-10-23 strong
betterleaks/betterleaks 2 adequate · 3 strong Go 101,331 lines 2,322 2026-10-23 strong
pay-rails/pay 4 strong Ruby 87,300 lines 2,263 2026-10-23 strong
mongodb/kingfisher 1 adequate · 3 strong Rust 279,321 lines 1,275 2026-10-28 strong
gitguardian/ggshield 1 adequate · 3 strong Python 117,171 lines 2,009 2026-10-23 strong
getkirby/kirby 1 adequate · 3 strong PHP 382,331 lines 1,535 2026-10-25 strong
always-open/laravel-totem 2 adequate · 3 strong PHP 17,071 lines 1,813 2026-10-23 strong
gitlab.com/graphviz/graphviz 4 strong — 244,282 lines 1,473 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.