How popular Go repos run GitHub Actions

Go gets caching almost for free (setup-go v4+ caches modules and build output by default), so the gaps in Go CI are usually elsewhere: no concurrency group, no job timeout, a scheduled workflow that's been red for weeks. Here is how the big Go projects actually score. Read the fix →

11Go repos scanned
1no dependency cache
11no job timeout
8no concurrency guard
0fully clean
RepoRuns (30d)CI min (30d)Recoverable min/moFailure rateFindings
gohugoio/hugopip47117.1k2,70011%12
caddyserver/caddygo2,5009,231*91614%18
cli/cligo2,5004,004*3184%19
gin-gonic/gingo1913518541%17
charmbracelet/bubbleteago349410693%22
junegunn/fzfgo72199333%9
go-gorm/gormgo2,500179*121%14
spf13/cobrago661622%7
spf13/vipergo841611%10
labstack/echogo1923,10005%5
pocketbase/pocketbasego73200%1

* CI min, recoverable min and failure rate cover only the latest 500 runs of a repo with more in 30 days.

Public data from each repo's GitHub Actions. Minutes are wall-clock workflow time over 30 days. These repos run Actions free (public repos always do). Each scorecard shows the private-repo dollar equivalent as a labeled estimate. Repo owners can remove their scorecard any time.

How does your Go repo compare?

Scan any public repo free, in seconds. No install, no card.

Scan a repo