# bloaty mit Homebrew, apk, dnf, MacPorts, Nix, pacman installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für bloaty in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:bloaty ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install bloaty ``` Evidenz: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install bloaty ``` Evidenz: MacPorts ports tree: devel/bloaty/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ### Linux - apk (92%): ```sh sudo apk add bloaty ``` Evidenz: Alpine Linux edge package indexes: bloaty from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz - dnf (92%): ```sh sudo dnf install bloaty ``` Evidenz: Fedora Rawhide package metadata: bloaty from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst - Nix (92%): ```sh nix profile install nixpkgs#bloaty ``` Evidenz: nixpkgs package indexes: pkgs/by-name/bl/bloaty/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman (92%): ```sh sudo pacman -S bloaty ``` Evidenz: Arch Linux sync databases: bloaty from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ## Paketfakten - **Paketschlüssel:** brew:bloaty - **Paketmanager:** Homebrew - **Version:** 1.1 - **Quellzusammenfassung:** Size profiler for binaries - **Homepage:** - **Repository:** - **Zuletzt aktualisiert:** 2026-06-20T05:07:42Z - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - bloaty (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 1.1 ## Projektgeschichte und Nutzung Bloaty, formally styled in its help text as Bloaty McBloatface, is Google's open source size profiler for binaries. It became a familiar package-manager utility for engineers who care about what actually makes an executable, library, firmware image, or WebAssembly artifact large. ### Projektgeschichte The official repository was created in 2016 and describes Bloaty as a size profiler for binaries. Its README frames the core question directly: finding what makes a binary big by showing size profiles across file size and virtual-memory size. Bloaty's implementation is unusually deep for a size-reporting CLI. The README and internals documentation describe custom ELF, DWARF, and Mach-O parsing, experimental PE/COFF and WebAssembly support, disassembly-assisted attribution, hierarchical profiles, size diffs, demangling, separate debug files, and custom data sources. The project reached Bloaty McBloatface v1.0 in August 2018 and v1.1 in May 2020. Its README also notes that it is not an official Google product, a common marker for Google-hosted open source tools that are useful outside their original internal context. ### Adoptionsgeschichte Bloaty's adoption followed the path of a specialist but widely useful developer tool: first-party docs and releases on GitHub, then packaging across major developer distributions. The input metadata records packages in Alpine apk, Homebrew, Fedora dnf, MacPorts, Nix, and Arch/pacman. Its cross-platform binary-format support helped adoption outside one operating-system niche. Engineers working on native applications, toolchains, mobile code, embedded binaries, and Wasm can all use the same CLI vocabulary to ask where bytes went. ### Wie es verwendet wird The basic workflow is `bloaty FILE`, optionally with `-d` data sources such as sections, symbols, segments, or compile units. Bloaty reports both file size and VM size because debug data, zero-initialized data, mapped segments, and metadata can affect disk and runtime footprints differently. A second major workflow is size diffing: users pass a current binary and a base binary separated by `--` to see exactly which sections, symbols, compile units, or other sources grew or shrank. That makes Bloaty especially attractive for release engineering and CI checks where size regressions need blameable output. ### Warum Paket-Nerds sich dafür interessieren Bloaty is package-nerd catnip because it explains package bloat with evidence instead of vibes. It bridges low-level object-file knowledge and everyday package maintenance by making debug sections, symbol tables, compile units, `.text`, `.rodata`, Mach-O load commands, and ELF program headers visible in a table humans can act on. The tool is also a useful counterweight to vague binary-size debates. Package maintainers can compare stripped and unstripped builds, bundled dependencies, LTO changes, debug-info packaging, static-linking choices, and architecture-specific output using one reproducible CLI. Compared with traditional tools such as `size`, `nm`, `objdump`, `readelf`, or linker map files, Bloaty packages several views into one profiler and preserves totals so the reported rows account for the whole file. That makes it unusually practical for maintainers who need to decide whether a size increase belongs in code, debug metadata, linked libraries, compiler output, or packaging policy. ### Zeitleiste - 2016: Official Google-hosted Bloaty repository created. - 2018: Bloaty McBloatface v1.0 released. - 2020: Bloaty McBloatface v1.1 released. - Package era: Bloaty appears across apk, Homebrew, dnf, MacPorts, Nix, and pacman according to package metadata. ### Related projects - `size`, `nm`, `objdump`, `readelf`, linker map files, and platform object-file tools are the traditional neighbors Bloaty complements. - ELF, DWARF, Mach-O, PE/COFF, and WebAssembly are the binary/debug formats named by Bloaty's official docs. - Bloaty bundles or can use dependencies including protobuf, RE2, Capstone, and pkg-config according to its README. ### Quellen - GitHub repository metadata via gh api repos/google/bloaty - - - - - source_facts.package-manager ## Sicherheitshinweise narrow executable package without higher-risk signals. - **Geiger-Risiko:** grün / niedrig - narrow executable package without higher-risk signals ## Andere Paketmanager-Einträge - Nix - bloaty: normalized package name match | nixpkgs package indexes: pkgs/by-name/bl/bloaty/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - apk - bloaty - 1.1-r32: normalized package name match | Alpine Linux edge package indexes: bloaty from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Bloaty McBloatface: a size profiler for binaries | https://github.com/google/bloaty - dnf - bloaty - 1.1-53.fc45: normalized package name match | Fedora Rawhide package metadata: bloaty from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | A size profiler for binaries | https://github.com/google/bloaty - pacman - bloaty - 1.1-26: normalized package name match | Arch Linux sync databases: bloaty from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Size profiler for binaries | https://github.com/google/bloaty - MacPorts - bloaty: normalized package name match | MacPorts ports tree: devel/bloaty/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/bloaty.yml](https://github.com/mxcl/pkgdb/blob/main/combined/bloaty.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph