(Lispex)

Every link on this page is pinned to the release shown below. The install scripts resolve the current release and compare the downloaded binary with its SHA-256 sidecar.

Release: v1.12.0

All platforms

Platform	Binary	Checksum
Linux · x86_64	lispex-linux-x86_64	.sha256
Linux · aarch64	lispex-linux-aarch64	.sha256
macOS · Apple silicon	lispex-macos-aarch64	.sha256
macOS · Intel	lispex-macos-x86_64	.sha256
Windows · x86_64	lispex-windows-x86_64.exe	.sha256
Release manifest	manifest.json	asset names, sizes, URLs, and SHA-256 digests

Optional macOS ARM64 route materials

Native routes fetch is the normal installation path. These immutable links expose the exact two companion archives and the catalog that the Native binary embeds, so you can audit or perform the documented offline installation without guessing a version.

Route	Archive	Checksum
Topaz VM companion	lispex-topaz-vm-aarch64-apple-darwin.zip	.sha256
Topaz AOT compiler companion	lispex-topaz-aot-compiler-aarch64-apple-darwin.zip	.sha256
Embedded route catalog	route-catalog.json	.sha256

One-line install

SHELL

# macOS / Linux
curl -fsSL https://www.lispex.com/install.sh | sh

# Windows (PowerShell)
irm https://www.lispex.com/install.ps1 | iex

# npm (Node 18+)
npm install -g lispex

Check the installed command

A successful install prints the exact product version. You can repeat the check at any time:

SHELL

lispex --version
# Expected: lispex v1.12.0

If the command is not found

macOS and Linux install to ~/.lispex/bin by default. Add that directory to PATH, then restart the shell.
Windows installs to %LOCALAPPDATA%\Lispex\bin by default. Add that directory to the user PATH, then open a new PowerShell window.
If you chose npm, confirm that Node 18 or newer is active and that the global npm binary directory is on PATH.

Which surface should I use?

Use the native binary for the dependency-free tree interpreter, explicit verified-bytecode Rust VM, Core IR and bytecode commands, exact Lispex Images, and the complete Lispex Vouch workflow including exact-source compiled artifacts and optional VM-agreement gates.
Use npm when Node is already available. It provides the same exact Lispex Image file commands through Rust/WASM, runs source, and authenticates Vouch evidence. It has no Core IR, bytecode, compiled-artifact reader, or VM engine; it does not issue, re-execute, or gate Vouch evidence.
Use the Playground without installing anything to run source or create, open, navigate, recover, download, and explicitly run exact images entirely in your browser. It has no Core IR or bytecode import and no VM engine, and exposes no Vouch artifacts, keys, authentication, or policy tools.

Optional Topaz routes

Compare verified bytecode or build a source-free AOT product

On macOS ARM64, Native can explicitly fetch the exact Topaz 5.11 VM and AOT compiler companions. The VM compares one verified bytecode artifact with Rust; the compiler builds a separate source-free AOT product using caller-supplied Rust tools. Installation never selects or executes a route, Rust remains the default, and no catalog, companion, result, or AOT product enters Vouch authority.

Lispex Images

Carry exact source as a deterministic image

Native and npm provide the same file commands; public WASM and the Playground use the same Rust codec locally. All restore source byte for byte and run only after full proof. Native accepts a proved image throughout Vouch; npm accepts it for identity, policy, and authenticated verification only. The image itself is not evidence or authority.

Lispex Vouch

Use Native when the decision must reach a local gate

Native can bind authenticated evidence to the exact source and input supplied outside a bundle, re-execute with current tree/Meaning, and grant only a matching local decision. When explicitly requested, it re-derives a compiled artifact from that source and also requires the verified Rust VM to agree. Unpinned bundles, ordinary bytecode, artifacts, and reports cannot promote themselves into authority.