C repositories

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 44 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
genymobile/scrcpy 3 adequate · 1 strong C 51,613 lines 150,783 2026-10-25 adequate
microsoft/powertoys 3 adequate · 1 strong C 1,051,102 lines 139,007 2026-10-25 adequate
allinurl/goaccess 3 adequate · 1 strong C 53,855 lines 21,119 2026-11-07 adequate
redis/redis 2 adequate · 3 strong C 549,207 lines 76,478 2026-10-25 strong
obsproject/obs-studio 2 adequate · 1 strong C 638,290 lines 76,625 2026-10-25 adequate
coturn/coturn 3 adequate · 2 strong C 92,203 lines 14,542 2026-11-07 adequate
openwall/john 3 adequate · 1 strong C 748,306 lines 13,879 2026-11-07 adequate
sumatrapdfreader/sumatrapdf 1 adequate · 3 strong C 2,359,429 lines 17,915 2026-11-03 strong
pymumu/smartdns 3 adequate · 2 strong C 106,256 lines 11,388 2026-11-07 adequate
tmux/tmux 2 adequate · 2 strong C 147,728 lines 49,513 2026-10-25 adequate
curl/curl 1 adequate · 3 strong C 469,729 lines 42,929 2026-10-25 strong
mpv-player/mpv 2 adequate · 1 strong C 272,141 lines 37,136 2026-10-25 adequate
jqlang/jq 1 adequate · 3 strong C 53,774 lines 35,703 2026-10-25 strong
raysan5/raylib 2 adequate · 1 strong C 397,357 lines 34,876 2026-10-25 adequate
nginx/nginx 1 adequate · 1 strong C 263,612 lines 31,767 2026-10-25 adequate
ggreer/the_silver_searcher 1 adequate · 2 strong C 9,215 lines 27,130 2026-10-25 adequate
libuv/libuv 3 strong C 120,178 lines 27,212 2026-10-25 adequate
valkey-io/valkey 1 adequate · 4 strong C 582,581 lines 27,314 2026-10-25 strong
radareorg/radare2 2 adequate · 2 strong C 1,205,860 lines 24,908 2026-10-25 adequate
jarun/nnn 2 adequate · 2 strong C 19,713 lines 22,016 2026-10-25 adequate
taosdata/tdengine 2 adequate · 3 strong C 1,958,618 lines 25,169 2026-10-23 strong
haproxy/haproxy 3 adequate · 1 strong C 516,419 lines 6,968 2026-11-03 adequate
neutrinolabs/xrdp 1 adequate · 2 strong C 207,190 lines 6,778 2026-11-03 adequate
timescale/timescaledb 3 strong C 334,644 lines 23,739 2026-10-22 adequate
3proxy/3proxy 2 adequate · 1 strong C 47,961 lines 5,572 2026-11-03 adequate
ossec/ossec-hids 2 adequate · 3 strong C 255,581 lines 5,070 2026-11-03 strong
winsiderss/systeminformer 2 adequate · 2 strong C 1,564,958 lines 16,315 2026-10-23 adequate
gojue/ecapture 3 adequate · 2 strong C 72,767 lines 15,516 2026-10-23 adequate
semgrep/semgrep 1 adequate · 3 strong C 1,526,065 lines 17,186 2026-10-22 strong
haiwen/seafile 2 adequate · 1 strong C 61,594 lines 15,371 2026-10-23 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.