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,018 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
openshiporg/openship 3 adequate · 1 strong TypeScript 88,200 lines 1,654 2026-10-23 adequate
frigadehq/trench 4 adequate · 1 strong TypeScript 6,113 lines 1,665 2026-10-23 adequate
saleor/storefront 3 adequate · 2 strong TypeScript 93,437 lines 1,635 2026-10-23 adequate
codeberg.org/river/river 2 adequate · 1 strong Zig 16,597 lines 1,258 2026-10-25 adequate
gitea.com/gitea/tea 2 adequate · 2 strong Go 35,678 lines 272 2026-11-07 adequate
hexpm/hexpm 3 adequate · 1 strong Elixir 171,982 lines 1,169 2026-10-25 adequate
owasp/wrongsecrets 3 adequate · 2 strong HTML 45,721 lines 1,473 2026-10-23 adequate
gitlab.com/es-de/emulationstation-de 3 adequate · 1 strong — 592,210 lines 248 2026-11-07 adequate
oca/web 2 adequate · 2 strong JavaScript 37,323 lines 1,240 2026-10-23 adequate
dromara/skyeye 3 adequate · 1 strong Java 440,473 lines 1,234 2026-10-23 adequate
pfelk/pfelk 3 adequate · 1 strong Shell 3,632 lines 1,222 2026-10-23 adequate
combodo/itop 2 adequate · 2 strong PHP 1,068,884 lines 1,207 2026-10-23 adequate
sev7enup/nodepilot 3 adequate · 2 strong C# 569,476 lines 102 2026-11-08 adequate
eirno/cracked-oura 4 adequate TypeScript 10,782 lines 419 2026-10-25 adequate
codeberg.org/codeberg/pages-server 3 adequate · 2 strong Go 6,699 lines 389 2026-10-25 adequate
mayur-esh/sigma-rules 1 adequate — 1,792 lines — 2026-10-29 adequate
rfgplk/micron.cpp 2 adequate · 1 strong C++ 716,818 lines 13 2026-10-04 adequate
th0rgal/open_health 3 adequate Swift 35,566 lines 19 2026-10-01 adequate
git.sr.ht/~xenrox/hut 2 adequate · 2 strong — 23,702 lines — 2026-10-25 adequate
baristaze/tadas 3 adequate · 2 strong Python 181,671 lines 3 2026-10-05 adequate
springernature/frontend-express-demo 3 adequate · 1 strong JavaScript 249 lines 2 2026-10-05 adequate
scottblodgett/sweetwater 3 adequate · 1 strong Python 28,274 lines — 2026-10-13 adequate
scottblodgett/voice-biomarker-poc 3 adequate TypeScript 1,372 lines — 2026-10-13 adequate
jagusgelos/factored-hackathon-2026-jagusgelos 3 adequate · 2 strong Python 49,390 lines — 2026-10-12 adequate
markbgilbert/aegis-zero-gc-benchmark 2 adequate · 1 strong Python 4,337 lines — 2026-10-06 adequate
aventine-labs/aegis-js 2 adequate TypeScript 4,238 lines — 2026-10-06 adequate
aventine-labs/testudo 1 adequate · 2 strong TypeScript 8,261 lines — 2026-10-06 adequate
nerolabs/brinybest 1 adequate · 1 strong Lua 3,362 lines — 2026-10-04 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.