# flamebearer mit Homebrew installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für flamebearer in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:flamebearer ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install flamebearer ``` Evidenz: local Homebrew formula metadata ## Paketfakten - **Paketschlüssel:** brew:flamebearer - **Paketmanager:** Homebrew - **Version:** 2.1.0 - **Quellzusammenfassung:** Blazing fast flame graph tool for V8 and Node - **Homepage:** - **Zuletzt aktualisiert:** 2026-06-27T12:34:32Z - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - flamebearer (Alias) - flamebearer-node (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 2.1.0 ## Projektgeschichte und Nutzung flamebearer is a JavaScript CPU trace analysis CLI for Chrome DevTools performance recordings and Node `.cpuprofile` files. The current README positions it as a compact text-summary tool rather than an HTML flame-graph renderer. ### Projektgeschichte The official GitHub repository was created in 2018 and was formerly available under Mapbox; GitHub now redirects the Mapbox URL to mourner/flamebearer. The README says version 1 generated an HTML flamegraph for Node traces, then the project lay dormant after 2018. In 2026 the project was revived with a new purpose: a CLI-oriented analyzer for performance optimization loops, especially useful for agents and humans reading CPU traces without opening a GUI. ### Adoptionsgeschichte The package's adoption niche is Node and browser performance work. It can be installed globally with npm, used through `flamebearer-node` to profile a script, or pointed at Chrome trace and Node CPU profile files. Its README explicitly leaves GUI flamegraph browsing to Speedscope and instead optimizes for one-page terminal summaries, drill-down flags, source-map support, hot source lines, and long-task visibility. ### Wie es verwendet wird Typical commands include `flamebearer-node bench.js`, `flamebearer profile.json.gz`, and `flamebearer CPU.*.cpuprofile`. Drill-down flags restrict stacks, threads, row counts, and time ranges. The tool does not document a persistent config file or credentials file; usage is command-line and profile-file driven. ### Warum Paket-Nerds sich dafür interessieren flamebearer is interesting because it changed identity without abandoning the package: from a Node HTML flamegraph generator inspired by earlier profiling tools into a fast textual trace summarizer aimed at modern command-line workflows. It sits in the flamegraph family tree but intentionally chooses a terminal-first UX, which makes it attractive for CI logs, scripted profiling runs, and automated performance investigations. ### Zeitleiste - 2018: Official repository created. - 2018: Version 1 era generated HTML flamegraphs for Node traces, according to the README. - 2026: Project revived as a CLI CPU trace analysis tool for agents and humans. ### Related projects - Brendan Gregg's FlameGraph is credited for the flamegraph concept. - 0x is credited as the original inspiration for the project. - Speedscope is named as the GUI flamegraph viewer that flamebearer does not try to replace. ### Quellen - - ## Sicherheitshinweise narrow executable package without higher-risk signals. - **Geiger-Risiko:** grün / niedrig - narrow executable package without higher-risk signals ## Combined YAML source View the package source record on GitHub. [combined/flamebearer.yml](https://github.com/mxcl/pkgdb/blob/main/combined/flamebearer.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph