Automic VaultAutomic Vault

brew

buildozer mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install buildozer

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Rewrite bazel BUILD files using standard commands

Befehle und Aliase

  • buildozer

Verlauf

Projektgeschichte und Nutzung

Buildozer is the command-line rewrite tool from Bazel's `buildtools` repository. It applies scripted edits to Bazel BUILD-like files, complementing Buildifier's formatting role with bulk, machine-checkable structural changes.

Projektgeschichte

The `bazelbuild/buildtools` repository was created on 2016-06-09 as a home for developer tools around Bazel BUILD files. Its top-level README groups Buildifier, Buildozer, and unused_deps together: formatter, editor, and Java dependency cleanup tool.

Buildozer's README defines it as a command-line tool for rewriting multiple Bazel BUILD files with standard commands. Its command language grew around labels, rule kinds, loads, attributes, comments, and later MODULE.bazel operations, reflecting the needs of large Bazel codebases where hand-editing BUILD files is slow and error-prone.

Adoptionsgeschichte

Buildozer's adoption is tied to Bazel adoption. Teams with large monorepos use it for mechanical BUILD-file migrations: adding dependencies, changing rule kinds, rewriting loads, deleting attributes, or applying edits across entire package trees.

Its availability through Homebrew and Nix makes it easy to install outside a Bazel source checkout, while Go module installation gives Bazel users a direct upstream-supported path.

Wie es verwendet wird

Typical usage is `buildozer 'command args' //pkg:target`, often repeated across many labels or fed from a command file. Buildozer can print modified files, format through Buildifier, run multiple commands in order, and process files in parallel.

The tool is most useful when a repository-wide BUILD migration should be expressed as a small, repeatable command instead of a one-off script that parses Starlark poorly.

Warum Paket-Nerds sich dafür interessieren

Buildozer is a package nerd tool because it encodes Bazel's BUILD-file editing semantics into a small CLI. It is the kind of utility that package managers carry so build-system maintainers can do tedious monorepo migrations without checking out a larger toolchain.

Its relationship with Buildifier is the key: one tool changes the syntax tree, the other normalizes the result. That pair became part of the everyday hygiene toolkit for serious Bazel repositories.

Zeitleiste

  • 2016: `bazelbuild/buildtools` repository is created.
  • 2016: Buildozer is distributed as one of the core tools in the Buildtools repository.
  • 2020s: Buildozer gains support for modern Bazel file shapes such as MODULE.bazel operations.
  • 2026: The Buildtools repository remains active as Bazel's formatter/editor tool collection.

Related projects

  • Buildozer is closely related to Bazel, Buildifier, unused_deps, Starlark BUILD files, MODULE.bazel, and monorepo migration tooling.

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

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
buildozercliglobales 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-Version8.5.1
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv8.5.1

https://github.com/bazelbuild/buildtools

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

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:buildozer
Version8.5.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/buildozer
Homepagehttps://github.com/bazelbuild/buildtools
Repositoryhttps://github.com/bazelbuild/buildtools
Upstream-Dokumentationhttps://github.com/bazelbuild/buildtools/blob/master/buildozer/README.md
LizenzApache-2.0
Quellarchivhttps://github.com/bazelbuild/buildtools/archive/refs/tags/v8.5.1.tar.gz
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namebuildozer
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.

Nix95%

buildozer

nix profile install nixpkgs#buildozer
  • normalized package name match
  • Abgeglichen nach: Buildozer
nixpkgs package indexes · raw.githubusercontent.com · nixpkgs package indexes: buildozer from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix

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 package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment