pkg.soopen package index

brew / Rang 2649

ibazel mit Homebrew, scoop installieren

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

InstallationsbefehlSicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install ibazel

local Homebrew formula metadata

Windows

Scoopverifiziert · 92%
scoop install extras/ibazel

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

Überblick

Paketzusammenfassung

Tools for building Bazel targets when source files change

Befehle und Aliase

  • ibazel

Verlauf

Projektgeschichte und Nutzung

ibazel is the executable from Bazel watcher, a source-file watcher for Bazel projects that reruns `build`, `test`, or `run` targets after source changes.

Projektgeschichte

The Bazel watcher README frames the tool around a familiar edit-save-rerun loop: save a file, have tests rebuild, or restart a server after source changes. The repository states that it is not an official Google product, while it lives under the `bazelbuild` GitHub organization and uses Bazel itself for builds.

Adoptionsgeschichte

ibazel became a common companion tool in Bazel-heavy developer workflows because it supplies the watch mode that many language-specific toolchains provide by default. Its README documents Homebrew, npm, Arch Linux AUR, and source-build installation paths, and Homebrew analytics show materially higher use than most packages in this batch.

Wie es verwendet wird

Developers run commands such as `ibazel build //path/to:target`, `ibazel test`, or `ibazel run` during active development. The output runner feature reads `%WORKSPACE%/.bazel_fix_commands.json` and can prompt for generated repair commands such as Buildozer or Gazelle invocations.

Warum Paket-Nerds sich dafür interessieren

ibazel is package-nerd candy because it sits at the boundary of build systems, file watching, editor feedback, live reload, npm distribution, Homebrew bottles, and Bazel's own repository culture. It is small enough to be a CLI utility, but important enough to show how a build ecosystem fills ergonomic gaps around a deliberately explicit core build tool.

Zeitleiste

  • v0.0.1: The repository contains an early public release tag.
  • 2017: The README's profiler example records iBazel and Bazel version data around a development-server reload workflow.
  • v0.15.x-v0.29.x: The tag history shows a long 0.x release series across the Bazel watcher repository.
  • 2026: The GitHub releases page lists v0.29.0 as an April 2026 release.

Related projects

  • The README connects ibazel directly to Bazel and mentions generated repair workflows involving Buildozer and Gazelle. Its npm package path, `@bazel/ibazel`, also ties it into JavaScript projects using Bazel.

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

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

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
%WORKSPACE%/.bazel_fix_commands.json
Windows
%WORKSPACE%/.bazel_fix_commands.json

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
ibazelExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

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-08-03
Manager-Version0.32.0
Manager aktualisiert2026-07-26
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:ibazel
Version0.32.0
PaketmanagerHomebrew
Homepagehttps://github.com/bazelbuild/bazel-watcher
Repositoryhttps://github.com/bazelbuild/bazel-watcher
Zuletzt aktualisiert2026-07-26T04:07:47+02:00
Pulseupdated
Bottlenicht erfasst
Dienstkeiner deklariert

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Scoop95%

extras/ibazel

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

Paketgraph

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

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
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation