Downloads

Every link on this page is pinned to the release shown below. The install scripts find the current release and compare the downloaded binary with the SHA-256 checksum file published beside it.

Release v1.18.0

All platforms

Optional extra engines for macOS ARM64

The usual way to install these is the Native routes fetch command. An extra engine here means another way of running Lispex that you install on purpose, and Lispex never picks one for you. These fixed links show the exact two companion archives and the catalog that the Native binary carries inside it, so you can audit them or follow the documented offline installation without guessing a version.

The smaller rule engine, exact bytes

Applications can pin the exact bytes of the same engine Native carries inside it, the one that runs a single rule under limits you declare and pulls in nothing from outside itself. Its manifest fixes what the engine covers, how it counts work, how values are passed in and out, what a receipt has to contain, its memory limits, and its checksum. Beside it sit recorded request and result bytes, so anyone using the engine can check that their own bytes come out exactly the same.

The whole-language rule engine, exact bytes

A separate component covers the whole language profile lispex-profile-1.5, and it carries its own identifiers for what it covers, how it counts work, the component itself, and the artifact. It reuses the ways of passing values in and out, the run transcript, and the shape of the record you can hand on, all of which were already found sufficient, without renaming or widening the smaller product. Native selects it only through explicit embed full commands and creates a fresh instance for every operation.

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 lispex

Check the installed command

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

lispex --version
# Expected: lispex v1.18.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 one should I use?

• Choose the native binary for the widest set of tools. It carries the built-in interpreter that reads your source directly and needs nothing else installed, a separate small engine that runs one rule under limits you declare, an explicit Rust virtual machine that runs verified bytecode, commands that show the intermediate forms a program is translated into, exact Lispex Images, and the whole Lispex Vouch workflow. Three things live only here, and they are issuing evidence, re-running the request you pinned, and the local gate check, which passes only when running the pinned rule on this machine still produces exactly the signed decision. Artifacts compiled from that same exact source belong to Native as well, and you can add an optional requirement that the virtual machine agree.
• Choose npm when Node is already available. It runs source, provides the same exact Lispex Image file commands through Rust compiled to WebAssembly, and authenticates Vouch evidence with the same checker Native uses. It has no intermediate-form or bytecode commands, no reader for compiled artifacts, and no virtual machine. In Vouch it authenticates, and it also replays a decision corpus, which compares recorded receipts offline and never re-runs the interpreter. What it refuses outright is issuing evidence, the re-execution option on verify, and the local gate check, and all three of those stay with Native.
• Use the Playground to run source, or to create, open, page through, recover, download, and explicitly run exact images, with no install and everything in your browser. It has no intermediate-form or bytecode import and no virtual machine, and it exposes no Vouch artifacts, keys, authentication, or policy tools.