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 →
| Repo | Runs (30d) | CI min (30d) | Recoverable min/mo | Failure rate | Findings |
|---|---|---|---|---|---|
| gohugoio/hugopip | 376 | 8,654 | 1,047 | 18% | 13 |
| junegunn/fzfgo | 359 | 798 | 303 | 1% | 20 |
| cli/cligo | 500+ | 1,515 | 138 | 5% | 27 |
| charmbracelet/bubbleteago | 207 | 429 | 98 | 12% | 18 |
| labstack/echogo | 87 | 729 | 73 | 0% | 7 |
| caddyserver/caddygo | 500+ | 758 | 65 | 2% | 21 |
| gin-gonic/gingo | 371 | 690 | 64 | 23% | 16 |
| pocketbase/pocketbasego | 54 | 249 | 25 | 0% | 3 |
| go-gorm/gorm | 500+ | 121 | 12 | 0% | 8 |
| spf13/cobrago | 96 | 21 | 1 | 0% | 7 |
| spf13/viper | 34 | 5 | 0 | 0% | 4 |
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.
Scan any public repo free, in seconds. No install, no card.
Scan a repo