Automic VaultAutomic Vault

brew

Install clang-build-analyzer with Homebrew, Nix

Tool to analyze compilation time. Version 1.6.0 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install clang-build-analyzer

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#clangbuildanalyzer

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

overview

Package summary

Tool to analyze compilation time

Commands and aliases

  • ClangBuildAnalyzer

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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?

Timeline

  • 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.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 8 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

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

Installed executables

CommandKindExposureNote
ClangBuildAnalyzercliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version1.6.0
manager updated
local dataok
upstreamcurrent
latest detectedv1.6.0

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

  • infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package keybrew:clang-build-analyzer
Version1.6.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/clang-build-analyzer
Homepagehttps://github.com/aras-p/ClangBuildAnalyzer
Repositoryhttps://github.com/aras-p/ClangBuildAnalyzer
Upstream docshttps://github.com/aras-p/ClangBuildAnalyzer#readme
LicenseUnlicense 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)
Source archivehttps://github.com/aras-p/ClangBuildAnalyzer/archive/refs/tags/v1.6.0.tar.gz
Build dependenciescmake
Uses from macOSllvm
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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 database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix92%

clangbuildanalyzer

nix profile install nixpkgs#clangbuildanalyzer
  • installed executable or alias match
  • Matched by: 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

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • 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