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
12no dependency cache
14no job timeout
14no concurrency guard
0fully clean
RepoRuns (30d)CI min (30d)Recoverable min/moFailure rateFindings
sharkdp/batcargo2602,27784326%11
biomejs/biomecargo500+2,5254594%31
actix/actix-webcargo3843,67937010%15
BurntSushi/ripgrepcargo10693036922%9
rust-lang/rust-analyzercargo500+3,0202424%20
serde-rs/serdecargo463831532%7
sharkdp/fdcargo6645614841%8
pola-rs/polarspip500+5,8801363%30
oven-sh/buncargo500+1,144801%13
vercel/turbocargo500+1,2745317%16
astral-sh/ruffpip500+2,085305%12
alacritty/alacrittycargo16611838%3
denoland/denopip500+19.2k621%14
clap-rs/clapcargo456639211%18
tokio-rs/tokiocargo500+6,94713%16

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