google/bloaty
Bloaty: a size profiler for binaries observed · 2026-10-15
Health v2 · maintenance only
66/100
- Activity 96
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-10-21. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3634
- days_rel: n/a
- days_push: 26
- n_releases_24m: 0
Adoption not part of the score
5563 stars · 379 forks observed · 2026-10-15
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Bloaty is a size profiler for binaries that shows what is taking up space inside an executable. It uses custom ELF, DWARF, and Mach-O parsers to attribute every byte of a binary to the symbol or compile unit that produced it.
Use cases
- find out what makes my binary big
- profile binary size by compile unit or symbol
- track binary size growth in CI with size diffs
- analyze which libraries bloat my executable
- attribute binary bytes to source files
- compare binary sizes between builds
When to choose
- you need to understand or reduce executable or library size
- you want automated binary size regression checks in CI
- you need per-symbol or per-compile-unit size attribution
When to avoid
- you need runtime performance profiling rather than size analysis
- you work with file formats outside ELF, Mach-O, PE/COFF, or WebAssembly
Facets
cli-tool · maturity active
developer-tools benchmarking parser developer-tools performance windows cli cpp binary-analysis size-profiling elf dwarf mach-o binary-size command-line linux macos
1 source
- readme: https://github.com/google/bloaty · fetched 2026-10-15 · 1a57cb2da1db
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| google/bloaty | main | 66 |
For agents
Data as of 2026-10-19T08:05:51.212177+00:00 · Report a problem