Automic VaultAutomic Vault

brew

bitwuzla mit Homebrew, Nix installieren

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

InstallationsbefehlSicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install bitwuzla

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#bitwuzla

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

Überblick

Paketzusammenfassung

SMT solver for bit-vectors, floating-points, arrays and uninterpreted functions

Befehle und Aliase

  • bitwuzla

Verlauf

Projektgeschichte und Nutzung

Bitwuzla is an SMT solver for fixed-size bit-vectors, floating-point arithmetic, arrays, uninterpreted functions, and combinations of those theories. Its name is an Austrian dialect joke meaning someone who tinkers with bits.

For package users, Bitwuzla is not just another CLI: it is a research-grade solver with a stable command-line interface, C/C++/Python APIs, and package-manager availability for reproducible formal-methods workflows.

Projektgeschichte

The Bitwuzla repository was created in 2020, and the project reached a public 0.1.0 release on June 30, 2023. The README asks users to cite the CAV 2023 Bitwuzla system-description paper by Aina Niemetz and Mathias Preiner.

Official documentation describes the command-line tool as supporting SMT-LIBv2 and non-sequential BTOR2 input files. The API documentation covers C++, C, Python, and OCaml documentation surfaces.

The installation docs identify CaDiCaL and SymFPU as required dependencies, with optional solver backends such as Kissat. The CLI exposes SAT-solver choices and solver controls that matter to verification researchers and benchmark runners.

Adoptionsgeschichte

The input package-manager data lists Homebrew and Nix packaging, which is a small but meaningful formal-methods footprint: these ecosystems are common in reproducible research and developer workstations.

Bitwuzla's adoption story is also academic. The official README points to the CAV 2023 publication and asks downstream users to report projects that incorporate Bitwuzla so they can be linked as third-party applications.

Wie es verwendet wird

CLI usage centers on feeding SMT-LIBv2 or BTOR2 files to bitwuzla, optionally producing models, unsat cores, interpolants, and solver statistics. The CLI can also parse-only, preprocess-only, set time and memory limits, choose SAT backends, and configure bit-vector solving options.

Library usage matters too: packages that install Bitwuzla make it available both as a command and as a dependency for tools that need embedded SMT solving.

Warum Paket-Nerds sich dafür interessieren

Bitwuzla is package-nerd significant because solver packaging is where reproducibility gets real: exact versions, linked SAT backends, Python bindings, and platform builds can change research and CI outcomes.

It also carries lineage value. The official references include SMT-LIB and BTOR2/Boolector literature, placing Bitwuzla in the bit-vector and hardware/software verification solver family rather than in generic theorem-proving packaging.

The 0.x release cadence through 2026 shows an actively moving solver, which makes package-manager freshness and dependency choices unusually important.

Zeitleiste

  • 2020: bitwuzla/bitwuzla repository created.
  • 2023-06-30: Bitwuzla 0.1.0 released.
  • 2023: Bitwuzla system-description paper published at CAV 2023.
  • 2024-12-13: Bitwuzla 0.7.0 released.
  • 2025-05-22: Bitwuzla 0.8.0 released.
  • 2026-05-21: Bitwuzla 0.9.1 released.

Related projects

  • SMT-LIB is the standard input language family documented by the CLI.
  • BTOR2 and Boolector are cited in the official references and define part of the bit-vector solver lineage around Bitwuzla.
  • CaDiCaL and SymFPU are required dependencies in the official installation docs; Kissat is documented as an optional dependency/SAT backend.

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.
  • Installiert mit 2 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 3 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
bitwuzlacliglobales 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-08
Manager-Version0.9.1
Manager aktualisiert2026-05-21
lokale DatenOK
Upstreamaktuell
neueste erkannte Version0.9.1

https://github.com/bitwuzla/bitwuzla

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:bitwuzla
Version0.9.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/bitwuzla
Homepagehttps://bitwuzla.github.io
Repositoryhttps://github.com/bitwuzla/bitwuzla
Upstream-Dokumentationhttps://bitwuzla.github.io/docs
LizenzMIT
Quellarchivhttps://github.com/bitwuzla/bitwuzla/archive/refs/tags/0.9.1.tar.gz
Zuletzt aktualisiert2026-05-21T19:21:27Z
Pulseupdated
Abhängigkeitengmp, mpfr
Build-Abhängigkeitenmeson, ninja, pkgconf
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 Namebitwuzla
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Nix95%

bitwuzla

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

Paketgraph

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

Verwandte Tools

  • mesonBuild dependency declared by Homebrew.
  • ninjaBuild dependency declared by Homebrew.
  • pkgconfBuild dependency declared by Homebrew.

Gleicher Workflow

  • stpShares av.db curated category or tags: cli, developer-tools, formal-methods, smt-solver.
  • cryptolShares av.db curated category or tags: cli, developer-tools, formal-methods.
  • proof-generalShares av.db curated category or tags: cli, developer-tools, formal-methods.
  • quintShares av.db curated category or tags: cli, developer-tools, formal-methods.
  • dafnyShares av.db curated category or tags: cli, developer-tools, formal-methods.
  • sbyShares av.db curated category or tags: cli, developer-tools, formal-methods.

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