RazrFalcon/cargo-bloat
Find out what takes most of the space in your executable. observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3160
- days_rel: n/a
- days_push: 845
- n_releases_24m: 0
Adoption not part of the score
2762 stars · 59 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A cargo subcommand that analyzes Rust executables to show which functions and crates take up the most space in the binary. It supports ELF, Mach-O, and PE binaries and offers regex filtering of results.
Use cases
- find what makes my rust binary large
- list biggest functions in an executable
- see which dependencies contribute most to binary size
- reduce rust executable size
- analyze .text section bloat
- filter binary size report by function name
When to choose
- you build Rust binaries and want per-function or per-crate size breakdowns
- you want a quick cargo-integrated tool with no extra setup
When to avoid
- you need WASM binary analysis - use twiggy instead
- you need exact, guaranteed-accurate size numbers (results are approximate)
Facets
cli-tool · maturity stable
developer-tools build-tool benchmarking developer-tools performance windows cli rust binary-size rust cargo-subcommand profiling command-line linux macos
2 sources
- readme: https://github.com/RazrFalcon/cargo-bloat · fetched 2026-08-28 · 05e3706b82cc
- registry_crates: https://crates.io/api/v1/crates/cargo-bloat · fetched 2026-08-29 · 392e03c4f98c
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| RazrFalcon/cargo-bloat | main | 32 |
For agents
markdown · JSON · MCP: product_card(name="RazrFalcon/cargo-bloat")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem