GitHub Actions CI benchmarks

"Is our CI normal?" is unanswerable without a fleet to compare against. These are real aggregates from the repos GitSpider watches — updated continuously, anonymized where the data isn't already public.

Config health across popular open-source repos

From GitSpider's public scans of 90 well-known open-source projects (the showcase) — the same handful of config gaps shows up everywhere.

851median CI-minutes / 30d
6.8%median failure rate
86%no concurrency guard
97%no job timeout
46%no dependency cache
0%fully clean config

Live numbers, recomputed as scans refresh. Every underlying scorecard is public — browse them by problem or by language:

Fix what the benchmarks flag

Each gap above has a focused how-to: concurrency, timeouts, caching, macOS runner cost, scheduled workflows — or start from all guides.

Where does your repo land?

Scan any public repo free — the scorecard shows your failure rate against this exact fleet ("better than ~X% of repos we watch").

Scan your repo