Repositories reading adequate

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 1,014 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
michalmuskala/jason 1 adequate · 2 strong Elixir 11,778 lines 1,680 2026-11-08 adequate
sparrowcode/permissionskit 2 adequate · 1 strong Swift 1,430 lines 5,810 2026-10-28 adequate
ponzu-cms/ponzu 3 adequate · 1 strong Go 26,224 lines 5,759 2026-10-28 adequate
postgres-ai/database-lab-engine 3 adequate · 2 strong Go 133,484 lines 2,786 2026-11-03 adequate
ctf-wiki/ctf-wiki 3 adequate · 1 strong Python 158,142 lines 9,729 2026-10-23 adequate
rustls/rustls 1 adequate · 2 strong Rust 88,522 lines 7,647 2026-10-25 adequate
checkmarx/kics 3 adequate · 2 strong Open Policy Agent 976,910 lines 2,730 2026-11-03 adequate
kaelio/ktx 4 adequate · 1 strong TypeScript 344,283 lines 1,628 2026-11-08 adequate
attify/firmware-analysis-toolkit 1 adequate · 2 strong Rust 249,207 lines 1,622 2026-11-08 adequate
higress-group/higress 3 adequate · 2 strong Go 553,319 lines 9,630 2026-10-23 adequate
gridaco/grida 2 adequate · 2 strong TypeScript 1,065,038 lines 2,696 2026-11-03 adequate
fthomas/refined 1 adequate · 2 strong Scala 14,267 lines 1,731 2026-11-07 adequate
readyouapp/readyou 3 adequate · 1 strong Kotlin 48,474 lines 7,559 2026-10-25 adequate
snyk/driftctl 2 adequate · 2 strong Go 275,993 lines 2,666 2026-11-03 adequate
risingwavelabs/risingwave 3 adequate · 2 strong Rust 1,196,119 lines 9,399 2026-10-23 adequate
activeloopai/deeplake 2 adequate · 2 strong C++ 252,241 lines 9,258 2026-10-23 adequate
open-pencil/open-pencil 3 adequate · 2 strong TypeScript 684,273 lines 9,218 2026-10-23 adequate
nhost/nhost 3 adequate · 2 strong TypeScript 977,425 lines 9,365 2026-10-23 adequate
bigbluebutton/bigbluebutton 4 adequate · 1 strong TypeScript 445,094 lines 9,250 2026-10-23 adequate
dicioteam/dicio-android 2 adequate · 2 strong Kotlin 25,723 lines 1,536 2026-11-08 adequate
gitcoffee-os/postbot 2 adequate · 1 strong TypeScript 20,671 lines 1,568 2026-11-07 adequate
peergos/peergos 2 adequate · 1 strong Java 201,099 lines 2,548 2026-11-03 adequate
jolibrain/deepdetect 3 adequate · 1 strong C++ 150,976 lines 2,551 2026-11-03 adequate
maximhq/bifrost 3 adequate · 2 strong Go 1,695,599 lines 9,051 2026-10-23 adequate
open-source-legal/opencontracts 4 adequate · 1 strong Python 1,118,493 lines 1,533 2026-11-08 adequate
sismics/docs 4 adequate · 1 strong JavaScript 118,907 lines 2,574 2026-11-03 adequate
semaphoreio/semaphore 3 adequate · 2 strong Elixir 1,200,122 lines 1,635 2026-11-07 adequate
parseablehq/parseable 4 adequate · 1 strong Rust 95,920 lines 2,570 2026-11-03 adequate
ssoready/ssoready 4 adequate · 1 strong TypeScript 78,880 lines 1,530 2026-11-08 adequate
kunzisoft/keepassdx 3 adequate · 1 strong Kotlin 110,294 lines 7,394 2026-10-25 adequate

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.