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
11no dependency cache
14no job timeout
12no concurrency guard
0fully clean
RepoRuns (30d)CI min (30d)Recoverable min/moFailure rateFindings
sharkdp/batcargo4185,0521,94217%11
denoland/denopip80316.4k*60820%15
biomejs/biomecargo2,5002,425*5434%32
sharkdp/fdcargo858683339%8
BurntSushi/ripgrepcargo565412167%9
pola-rs/polarspip2,5006,340*1993%29
rust-lang/rust-analyzercargo1,6772,082*1705%20
vercel/turbocargo2,5002,069*12816%16
oven-sh/buncargo2,500695*965%17
serde-rs/serdecargo37103413%7
astral-sh/ruffpip2,5001,844*324%13
actix/actix-webcargo1,4244,487*313%14
alacritty/alacrittycargo171013012%3
tokio-rs/tokiocargo2,4507,464*06%15
clap-rs/clapcargo387486026%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