How popular Rust repos run GitHub Actions

Rust compile times make CI config matter more than in any other stack: an uncached cargo build or a superseded run that never gets cancelled costs real minutes. The de-facto fix is Swatinem/rust-cache. Here is how well-known Rust projects actually run CI. Read the fix →

15Rust repos scanned
10no dependency cache
13no job timeout
13no concurrency guard
0fully clean
RepoRuns (30d)CI min (30d)Recoverable min/moFailure rateFindings
sharkdp/batcargo3713,3561,27422%11
vercel/turbocargo2,5006,718*55719%6
BurntSushi/ripgrepcargo1931,2244894%9
biomejs/biomecargo2,5002,111*3962%23
sharkdp/fdcargo11973627913%8
rust-lang/rust-analyzercargo1,6872,680*2212%20
pola-rs/polarspip2,5007,165*2149%26
tokio-rs/tokiocargo2,21910.5k*2126%18
denoland/denopip3786,9479711%10
oven-sh/buncargo2,5002,482*901%18
alacritty/alacrittycargo421566314%5
astral-sh/ruffpip2,5002,625*491%18
serde-rs/serdecargo441024130%7
actix/actix-webcargo1,6142,915*304%15
clap-rs/clapcargo248276021%13

* 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 Rust repo compare?

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

Scan a repo