(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.8.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

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

Which surface should I use?

Use the native binary for exact Lispex Image encode, inspect, decode, and explicit image execution, plus the dependency-free interpreter and complete Lispex Vouch workflow.
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 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 exposes no Vouch artifacts, keys, authentication, or policy tools.

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 that request with the current interpreter, and grant only a matching local decision. Unpinned bundle verification remains authentication-only, and reports or bundle bytes cannot promote themselves into execution authority.