Go 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 316 surveyed
Sort Relevance Newest Stars Lines of code Files History Findings Worst band
RepositoryLanguageSizeStarsReadBand
gruntwork-io/terragrunt 3 adequate · 1 strong Go 469,261 lines 9,859 2026-10-25 adequate
earthly/earthly 4 strong Go 107,129 lines 12,054 2026-10-23 adequate
paca-ai/paca 3 adequate · 2 strong Go 531,598 lines 2,020 2026-11-08 adequate
owncast/owncast 1 adequate · 4 strong Go 192,134 lines 11,624 2026-10-23 strong
cyclops-ui/cyclops 4 adequate · 1 strong Go 48,593 lines 3,320 2026-11-03 adequate
vinceanalytics/vince 4 adequate · 1 strong Go 27,231 lines 2,010 2026-11-07 adequate
featureform/featureform 2 adequate · 3 strong Go 189,948 lines 1,991 2026-11-08 adequate
anchore/grype 3 adequate · 1 strong Go 203,369 lines 13,087 2026-10-22 adequate
storj/storj 2 adequate · 3 strong Go 834,667 lines 3,284 2026-11-03 strong
vouch/vouch-proxy 1 adequate · 4 strong Go 9,985 lines 3,281 2026-11-03 strong
open-telemetry/opentelemetry-go 2 adequate · 2 strong Go 986,048 lines 6,585 2026-10-28 adequate
elastic/beats 3 adequate · 2 strong Go 2,365,122 lines 12,653 2026-10-22 adequate
daptin/daptin 3 adequate · 2 strong Go 249,874 lines 1,898 2026-11-07 adequate
dtm-labs/dtm 2 adequate · 3 strong Go 21,491 lines 10,923 2026-10-23 strong
tyktechnologies/tyk 3 adequate · 2 strong Go 464,565 lines 10,870 2026-10-23 adequate
crossplane/crossplane 1 adequate · 4 strong Go 177,826 lines 12,189 2026-10-22 strong
kedacore/keda 1 adequate · 4 strong Go 217,273 lines 10,657 2026-10-23 strong
screego/server 3 adequate · 2 strong Go 6,439 lines 10,738 2026-10-23 adequate
root-gg/plik 2 adequate · 3 strong Go 92,728 lines 1,839 2026-11-07 strong
fwdcloudsec/granted 1 adequate · 3 strong Go 16,642 lines 1,810 2026-11-07 strong
lf-edge/ekuiper 2 adequate · 3 strong Go 305,770 lines 1,747 2026-11-08 strong
hatchet-dev/hatchet 3 adequate · 2 strong Go 875,785 lines 8,034 2026-10-25 adequate
kube-logging/logging-operator 2 adequate · 3 strong Go 192,507 lines 1,716 2026-11-08 strong
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
krakend/krakend-ce 2 adequate · 3 strong Go 5,635 lines 2,702 2026-11-03 strong
higress-group/higress 3 adequate · 2 strong Go 553,319 lines 9,630 2026-10-23 adequate
goplus/xgo 1 adequate · 3 strong Go 89,812 lines 9,487 2026-10-23 strong
snyk/driftctl 2 adequate · 2 strong Go 275,993 lines 2,666 2026-11-03 adequate
absmach/magistrala 2 adequate · 3 strong Go 119,482 lines 2,658 2026-11-03 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.