Installation

Chainvet ships four binaries — the chainvet CLI plus the optional chainvet-ci, chainvet-server, and chainvet-lsp front ends. All of them dynamically link the Z3 solver library, which the installer provides.

One-line install (Linux x86_64)

curl -fsSL https://install.chainvet.dev/install.sh | sh

On a real terminal this shows an arrow-key checkbox menu to pick which components to install (↑/↓ to move, space to toggle, enter to confirm) — the chainvet CLI is preselected. Terminals that can't enter raw mode fall back to a numbered prompt (force it with CHAINVET_MENU=basic).

The installer picks components, installs the Z3 runtime via your system package manager (apt / dnf / pacman / zypper / apk), downloads each selected binary, verifies it against SHA256SUMS.txt, and installs it.

Scripted / non-interactive installs

Piped or non-interactive runs install just the CLI unless CHAINVET_BINS says otherwise, so automation stays deterministic:

# everything, no prompt
curl -fsSL https://install.chainvet.dev/install.sh | CHAINVET_BINS=all sh

# just the CLI + language server
curl -fsSL https://install.chainvet.dev/install.sh | CHAINVET_BINS="chainvet chainvet-lsp" sh

The installer is configured entirely through environment variables:

Build from source

Building requires a Rust toolchain and the Z3 system library.

# Debian/Ubuntu:
sudo apt-get install libz3-dev
# macOS:
brew install z3

git clone https://github.com/chainvet/chainvet
cd chainvet

The CLI is the core tool; the CI, server, and LSP front ends are optional and pull extra dependencies. Use -p to build only what you want:

# CLI only — just the `chainvet` analyzer
cargo build --release -p chainvet-cli

# CLI plus whichever front ends you want (mix and match)
cargo build --release -p chainvet-cli -p chainvet-ci       # + SARIF / CI
cargo build --release -p chainvet-cli -p chainvet-server   # + REST server
cargo build --release -p chainvet-cli -p chainvet-lsp      # + language server

# everything — all four binaries
cargo build --release

Each -p chainvet-<name> produces target/release/chainvet-<name> (the CLI's binary is just chainvet).

You can also install a single front end straight from Git:

cargo install --git https://github.com/chainvet/chainvet chainvet-cli

Verify the install

chainvet --version

If the binary isn't found, make sure the install directory (for example ~/.local/bin) is on your PATH.

Optional: PDF reports

Generating PDF audit reports (chainvet scan -f pdf) needs an HTML→PDF engine on your PATH — weasyprint (recommended) or wkhtmltopdf. Markdown and HTML reports need nothing extra. See Audit reports.

Next steps