Automic VaultAutomic Vault

brew

bom mit Homebrew, Nix, zypper, scoop installieren

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

InstallationsbefehlSicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install bom

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#bom

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

openSUSE zypperverifiziert · 92%
sudo zypper install bom

openSUSE Tumbleweed package metadata · bom · Quelle: download.opensuse.org

Windows

Scoopverifiziert · 92%
scoop install main/bom

Scoop official bucket manifest trees · bucket/bom.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Utility to generate SPDX-compliant Bill of Materials manifests

Befehle und Aliase

  • bom

Verlauf

Projektgeschichte und Nutzung

bom is the Kubernetes SIGs SBOM multitool for creating, viewing, and transforming Software Bills of Materials, especially SPDX documents.

Projektgeschichte

The official README says bom was created as part of the effort to create an SBOM for the Kubernetes project. It later became a general-purpose CLI that can generate SPDX packages from directories, container images, single files, archives, and other sources.

The project is associated with the Linux Foundation's Automating Compliance Tooling Technical Advisory Council, placing it in the supply-chain compliance tooling ecosystem rather than only in Kubernetes internals.

Adoptionsgeschichte

bom's adoption follows the post-SolarWinds supply-chain tooling wave: SBOMs became expected release artifacts, and Kubernetes needed tooling that could fit CI, container images, Go dependency analysis, SPDX output, and in-toto provenance workflows. The input package facts list Homebrew, Nix, Scoop, and zypper packaging.

Wie es verwendet wird

Common usage is `bom generate` against a directory, file list, archive, or image, then `bom document` to inspect or query the resulting SPDX document. The README also documents license classification, `.gitignore` support, Go dependency analysis, and provenance export.

Warum Paket-Nerds sich dafür interessieren

bom is package-nerd significant because it is tooling about packages themselves: it turns source trees, images, and dependencies into machine-readable supply-chain metadata. It sits where package management, compliance, SPDX, Kubernetes release engineering, and container provenance meet.

Zeitleiste

  • 2021: bom appears in Kubernetes SIG tooling around the Kubernetes SBOM effort.
  • 2020s: bom grows into a general-purpose SPDX SBOM generator for files, directories, archives, container images, and Go dependencies.
  • 2020s: The project is incubated under the Linux Foundation Automating Compliance Tooling TAC.

Related projects

  • Related projects include Kubernetes, SPDX, in-toto, Syft, CycloneDX tooling, cosign, and other software supply-chain inventory tools.

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
bomcliglobales 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-Version0.7.1
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.7.1

https://github.com/kubernetes-sigs/bom

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

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:bom
Version0.7.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/bom
Homepagehttps://kubernetes-sigs.github.io/bom/
Repositoryhttps://github.com/kubernetes-sigs/bom
Upstream-Dokumentationhttps://kubernetes-sigs.github.io/bom
LizenzApache-2.0
Quellarchivhttps://github.com/kubernetes-sigs/bom/archive/refs/tags/v0.7.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 Namebom
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%

bom

nix profile install nixpkgs#bom
  • normalized package name match
  • Abgeglichen nach: Bom
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/bo/bom/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
zypper95%

bom 1.0.1-1.15

Deals with Unicode byte order marks

https://github.com/archiecobbs/bom

sudo zypper install bom
  • License: Apache-2.0
  • Category: Productivity/File utilities
  • Architecture: x86_64
  • Source Package: bom
  • 1 Abhängigkeiten
  • 1 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Bom
openSUSE Tumbleweed package metadata · download.opensuse.org · openSUSE Tumbleweed package metadata: bom from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst
Scoop95%

main/bom

scoop install main/bom
  • normalized package name match
  • Abgeglichen nach: Bom
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/bom.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

Verwandte Tools

  • goBuild dependency declared by Homebrew.

Gleicher Workflow

  • bomctlShares av.db curated category or tags: cli, sbom, security, software-supply-chain, spdx.
  • cdxgenShares av.db curated category or tags: cli, sbom, security, software-supply-chain, spdx.
  • cyclonedx-cliShares av.db curated category or tags: cli, sbom, security, software-supply-chain, spdx.
  • chainloop-cliShares av.db curated category or tags: cli, sbom, security, software-supply-chain.
  • cve-bin-toolShares av.db curated category or tags: cli, sbom, security, software-supply-chain.
  • cyclonedx-gomodShares av.db curated category or tags: cli, sbom, security, software-supply-chain.

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