Automic VaultAutomic Vault

brew

clang-build-analyzer mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für clang-build-analyzer in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install clang-build-analyzer

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#clangbuildanalyzer

nixpkgs package indexes · pkgs/by-name/cl/clangbuildanalyzer/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Tool to analyze compilation time

Befehle und Aliase

  • ClangBuildAnalyzer

Verlauf

Projektgeschichte und Nutzung

Clang Build Analyzer is a C and C++ build analysis tool that aggregates Clang -ftime-trace JSON files and reports where compilation time is spent. It is a package-nerd tool for people optimizing slow native builds rather than a general application framework.

Projektgeschichte

The repository was created in August 2019 after Clang 9 introduced -ftime-trace. The README says the tool takes the single-file trace output generated by Clang and aggregates many compilation traces into summaries of slow files, templates, functions, code generation, and expensive headers.

Adoptionsgeschichte

The supplied package-manager data lists Homebrew and Nix packaging. Release metadata shows an initial 1.0.0 release labeled 'Initial release' and later releases tracking newer Clang support, including Clang 19 support in 1.6.0.

Wie es verwendet wird

A typical workflow starts capture with ClangBuildAnalyzer --start, builds with Clang 9 or later using -ftime-trace, stops capture with --stop, and runs --analyze on the produced capture file. A ClangBuildAnalyzer.ini file in the working directory controls how many expensive files, templates, functions, and headers are reported.

Warum Paket-Nerds sich dafür interessieren

It matters because it packages a practical workflow around a compiler diagnostic format. For large C++ codebases, it turns a pile of per-object JSON traces into actionable package-maintainer and build-engineer questions: which headers, templates, source files, or compiler phases are costing rebuild time?

Zeitleiste

  • 2019: Repository created after Clang 9 documented -ftime-trace.
  • 2020: v1.0.0 initial release published on GitHub.
  • 2020: v1.2.0 focused on optimizations for large builds.
  • 2023: v1.5.0 improved expensive-header information.
  • 2025: v1.6.0 added Clang 19 support and fixes.

Related projects

  • Related projects include Clang, LLVM, Clang's -ftime-trace support, Chrome trace viewers, speedscope.app, and native build systems such as Make, CMake, Xcode, and Visual Studio.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 8 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
./ClangBuildAnalyzer.ini

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
ClangBuildAnalyzercliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version1.6.0
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.6.0

https://github.com/aras-p/ClangBuildAnalyzer

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:clang-build-analyzer
Version1.6.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/clang-build-analyzer
Homepagehttps://github.com/aras-p/ClangBuildAnalyzer
Repositoryhttps://github.com/aras-p/ClangBuildAnalyzer
Upstream-Dokumentationhttps://github.com/aras-p/ClangBuildAnalyzer#readme
LizenzUnlicense AND Zlib AND MIT AND BSL-1.0 AND BSD-3-Clause AND Apache-2.0 AND BSD-2-Clause AND (Apache-2.0 WITH LLVM-exception)
Quellarchivhttps://github.com/aras-p/ClangBuildAnalyzer/archive/refs/tags/v1.6.0.tar.gz
Build-Abhängigkeitencmake
Von macOS bereitgestellte Bibliothekenllvm
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameclang-build-analyzer
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix92%

clangbuildanalyzer

nix profile install nixpkgs#clangbuildanalyzer
  • installed executable or alias match
  • Abgeglichen nach: Clangbuildanalyzer
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/cl/clangbuildanalyzer/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment