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.16.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 |
Exact bounded evaluator
Applications can pin the same import-free evaluator bytes that Native embeds. The manifest fixes its profile, meter, ABI, value codec, receipt contract, memory bounds, and digest; the golden vectors let an independent consumer check canonical request and result bytes.
| Binary | Checksum |
|---|---|
| Import-free evaluator Wasm · lispex-embed-evaluator.wasm | .sha256 |
| Evaluator component manifest · lispex-embed-evaluator-manifest.json | .sha256 |
| Canonical golden vectors · lispex-embed-evaluator-golden-vectors.json | .sha256 |
| Restricted evaluator redistribution · lispex-embed-evaluator-redistribution.zip | .sha256 |
Exact full-profile bounded evaluator
The separate full component covers lispex-profile-1.5 with its own semantic-profile, meter, component, and artifact identities. It reuses the sufficient ABI, value codec, transcript, and portable-core schemas without renaming or expanding the restricted product. Native selects it only through explicit embed full commands and creates a fresh instance for every operation.
| Binary | Checksum |
|---|---|
| Import-free full-profile evaluator Wasm · lispex-full-embed-evaluator.wasm | .sha256 |
| Full evaluator component manifest · lispex-full-embed-evaluator-manifest.json | .sha256 |
| Full provider vectors · lispex-full-embed-evaluator-provider-vectors.json | .sha256 |
| Full evaluator redistribution · lispex-full-embed-evaluator-redistribution.zip | .sha256 |
One-line install
# 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 lispexCheck the installed command
A successful install prints the exact product version. You can repeat the check at any time:
lispex --version
# Expected: lispex v1.16.0If 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?
- Choose the native binary for the dependency-free tree interpreter, the restricted bounded embed evaluator, the explicit verified-bytecode Rust VM, Core IR and bytecode commands, exact Lispex Images — and the whole Lispex Vouch workflow. Issuing, request-bound re-execution, and the local gate live only here, including exact-source compiled artifacts with an optional VM-agreement requirement.
- Choose npm when Node is already available. It runs source, provides the same exact Lispex Image file commands through Rust/WASM, and authenticates Vouch evidence with the same verifier Native uses. It has no Core IR, bytecode, compiled-artifact reader, or VM engine — and its Vouch role ends at authentication: no issuing, no re-execution, no gate.
- Use the Playground to run source, or to create, open, navigate, recover, download, and explicitly run exact images — no install, everything in your browser. It has no Core IR or bytecode import and no VM engine, and it 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 against Rust; the compiler builds a separate source-free AOT product with caller-supplied Rust tools. Installing them selects and executes nothing — Rust stays the default — and no catalog, companion, comparison result, or AOT product ever enters Vouch authority.
Lispex Images
Carry exact source as a deterministic image
Native and npm share the same image file commands; public WASM and the Playground run the same Rust codec locally. Every surface restores source byte for byte and executes it only after full canonical proof. Native accepts a proved image throughout the Vouch workflow; npm accepts it for identity, policy, and authenticated verification only. The image itself is a carrier — never evidence, never authority.
Lispex Vouch
Use Native when a decision must reach a local gate
Native binds authenticated evidence to the exact source and input you supply outside the bundle, re-executes on the current tree and Meaning paths, and grants only a matching local decision. On explicit request it also re-derives a compiled artifact from that same source and requires the verified Rust VM to agree. Unpinned bundles, ordinary bytecode, artifacts, and reports cannot promote themselves into authority.