Cargo
Leaderboard

A heavyweight Rust competition

That’s a lot
of target/.

Rust builds take up space. Compare your build artifacts, biggest cleans, and longest waits.

What are we measuring?

One debug build in an empty directory. Temporary artifacts removed afterward.

Loading…
Fresh Rust builds, ranked by artifact bytes
Rank Project / builder Fresh build size Build time Recorded

Weighing the competition.

Fetching the latest community entries.

Personal best per project. All time.GitHub accounts. Self-reported scores.

Put your project
on the scales.

Your agent installs the CLI, connects GitHub, and submits your first fresh build. Start with the prompt.

Your GitHub account, project label, measurements, platform, tool versions, revision and benchmark flags are public. Source code and local paths stay on your machine.

Read the CLI guide
Agent setup
Paste into your coding agent

Open your Rust project in Codex, Claude Code, or another coding agent with terminal access. 

Set up Cargo Leaderboard in this Rust project using https://cargo.lwn.lol/agents.md, then run a fresh-build benchmark and verify the submission.
Read the agent instructions
Prefer a terminal? Manual setup

Prebuilt binary, checksum verified. Requires Rust to build your projects.

1. Install 
curl -fsSL https://cargo.lwn.lol/install.sh -o /tmp/cargo-leaderboard-install.sh &&
sh /tmp/cargo-leaderboard-install.sh
2. Connect your GitHub account 
cargo leaderboard login --api-url https://cargo.lwn.lol
3. Run inside your Rust project 
cargo leaderboard benchmark
cargo leaderboard clean

Benchmark removes its temporary artifacts; your existing build folder stays intact. Clean deletes your build artifacts, just like cargo clean. Setup trouble? Run cargo leaderboard doctor.

How the scores work.

Fresh builds start empty.

Benchmark runs one debug build in an isolated directory, counts its artifacts, then removes them. Existing caches and earlier builds stay on the separate Build folders board, including all scores from before fresh benchmarks launched.

Cleans give it back.

The before-and-after difference is your clean score. Partial cleans count only the decrease. Empty cleans don’t rank. Values use binary units: 1 GiB is 1,073,741,824 bytes.

Compare the context, too.

Rust versions, platforms, features and project profile settings still vary. Open Build details to see the revision and flags. Times depend on your machine and download caches. Sizes are logical bytes, not allocated disk blocks. GitHub accounts are verified; scores are self-reported.

Keeping a project private? Use --repo my-project to replace its label, or --no-submit to measure locally. Put wrapper options before Cargo flags.