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 | 471 | 17.1k | 2,700 | 11% | 12 |
| caddyserver/caddygo | 2,500 | 9,231* | 916 | 14% | 18 |
| cli/cligo | 2,500 | 4,004* | 318 | 4% | 19 |
| gin-gonic/gingo | 191 | 351 | 85 | 41% | 17 |
| charmbracelet/bubbleteago | 349 | 410 | 69 | 3% | 22 |
| junegunn/fzfgo | 72 | 199 | 33 | 3% | 9 |
| go-gorm/gormgo | 2,500 | 179* | 12 | 1% | 14 |
| spf13/cobrago | 66 | 16 | 2 | 2% | 7 |
| spf13/vipergo | 84 | 16 | 1 | 1% | 10 |
| labstack/echogo | 192 | 3,100 | 0 | 5% | 5 |
| pocketbase/pocketbasego | 7 | 32 | 0 | 0% | 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.
Scan any public repo free, in seconds. No install, no card.
Scan a repo