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.7.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 lispexWhich surface should I use?
- Use the native binary for the dependency-free interpreter and the complete Lispex Vouch workflow, including issue, authenticated verification, re-execution, and a local gate.
- Use npm when Node is already available. It runs Lispex, inspects and replays Vouch artifacts, authenticates raw or bundled evidence, derives exact identities, and creates or checks consumer policy. It does not issue, re-execute, or gate.
- Use the Playground for quick snippets without installing anything. It evaluates code but does not expose Vouch artifacts, keys, authentication, or policy tools.
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.