Automic VaultAutomic Vault

brew

alive2 mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install alive2

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#alive2

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

Überblick

Paketzusammenfassung

Automatic verification of LLVM optimizations

Befehle und Aliase

  • alive
  • alive-exec
  • alive-jobserver
  • alive-tv
  • quick-fuzz

Verlauf

Projektgeschichte und Nutzung

Alive2 is a toolkit for analyzing and verifying LLVM code and transformations, centered on translation validation for compiler optimizations.

Projektgeschichte

The public Alive2 repository starts with an initial commit on 2018-06-09. Its README describes libraries for Alive2 IR, symbolic execution, LLVM-to-Alive2 IR conversion, refinement checking, and SMT abstraction, plus tools including an Alive drop-in replacement, alive-tv, alive-exec, and clang/opt translation-validation plugins.

The project positions itself as the successor in spirit to Alive for LLVM optimization reasoning, but with a broader toolkit around real LLVM IR and translation validation. The README points to the PLDI 2021 Alive2 paper for the technical introduction.

Alive2 tracks LLVM closely: its README says the latest Alive2 is intended to build against the latest LLVM main branch, and its later release tags use LLVM-version-like labels such as v19.0, v20.0, and v21.0.

Adoptionsgeschichte

Alive2 is used as an LLVM quality tool rather than a general application. The README says the maintainers run translation validation across LLVM IR-level transformation tests on LLVM main each day and publish results. The repository's BugList lists many LLVM and Z3 issues found by Alive2.

The project also has an online alive-tv instance, letting compiler developers try translation validation without building the local toolchain.

Wie es verwendet wird

Package users usually run alive-tv on source and target LLVM IR, wrap opt through Alive2's translation-validation scripts, or compile through alivecc/alive++ to validate IR-level transformations performed by clang. alive-exec is documented as an experimental UB-precise LLVM function interpreter.

The toolchain is intentionally low-level: it needs CMake, a C/C++ compiler, re2c, Z3, and often a matching LLVM build with RTTI and exceptions enabled.

Warum Paket-Nerds sich dafür interessieren

Alive2 is notable in package-manager catalogs because it packages research-grade compiler verification as command-line tools. For LLVM-heavy users, installing alive-tv is a practical way to test optimizer correctness without assembling the whole research environment by hand.

It also depends on the exact moving edge of LLVM, which makes it a good example of a package whose value is tied to keeping versions and build flags aligned with upstream compiler development.

Zeitleiste

  • 2018: Public Git history begins with an initial commit.
  • 2020: README example documents an LLVM release/10.x optimizer bug found by alive-tv.
  • 2021: PLDI 2021 paper published as the project's technical introduction.
  • 2024: v19.0 tag appears in the repository history.
  • 2025: v21.0 tag appears in the repository history.

Related projects

  • LLVM: primary compiler IR and optimization target.
  • Z3: SMT solver dependency and one of the projects whose bugs are tracked in Alive2's BugList.
  • Alive: earlier optimization-verification tool referenced by Alive2's drop-in replacement.

Quellen

  • Alive2 PLDI 2021 paper linked from README: https://web.ist.utl.pt/nuno.lopes/pubs/alive2-pldi21.pdf
  • Git history from https://github.com/AliveToolkit/alive2.git
  • Official Alive2 BugList: https://raw.githubusercontent.com/AliveToolkit/alive2/master/BugList.md
  • Official Alive2 README: https://raw.githubusercontent.com/AliveToolkit/alive2/master/README.md

Sicherheitslage

Risikostufe: blue

broad file, network, media, or database tool signal.

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

  • broad file, network, media, or database tool signal

Signale

  • text:server

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 4 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 2 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
alivecliglobales Executable
alive-execcliglobales Executable
alive-jobservercliglobales Executable
alive-tvcliglobales Executable
quick-fuzzcliglobales 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-10
Manager-Version21.0
Manager aktualisiert2026-06-22
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/AliveToolkit/alive2

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:alive2
Version21.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/alive2
Homepagehttps://github.com/AliveToolkit/alive2
Repositoryhttps://github.com/AliveToolkit/alive2
Upstream-Dokumentationhttps://alive2.llvm.org/ce
LizenzMIT
Quellarchivhttps://github.com/AliveToolkit/alive2.git
Zuletzt aktualisiert2026-06-22T14:02:42-07:00
Pulseupdated
Abhängigkeitenhiredis, llvm, z3, zstd
Build-Abhängigkeitencmake, re2c
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 Namealive2
Version Scheme0
Revision4
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%

alive2

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

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