Skip to content
Chock

Download

Two channels, both served by GitHub

Every file comes from the project's own release workflow, and GitHub serves it. This site holds no binaries.

Stable

nothing tagged yet

Chock is pre-alpha and has cut no tagged release yet. Build it from source in the meantime.

Linux x86_64

x86_64-linux

No file for this target.

Linux ARM64

aarch64-linux

No file for this target.

macOS Apple Silicon

aarch64-macos

No file for this target.

Unstable

0.1.0-unstable-20260927-0b3e3a5, 27 September 2026

A prerelease of what the project is working on today. Expect it to change. Read what changed.

macOS Apple Silicon

aarch64-macos

No file for this target.

Check what you got against SHA256SUMS: sha256sum -c SHA256SUMS --ignore-missing

Every releaseThe source

This page is written when the site is built, so a new release appears once a build has run. The releases page is always current.

After the download

Each archive unpacks into a directory holding the program, the licence and the readme. Run chock doctor before anything else. It measures each sandbox layer on this machine and says which are on, so you know what holds on this machine before the first task.

~/Downloads
# check the archive against the digest file$ sha256sum -c SHA256SUMS --ignore-missing$ tar xzf chock-x86_64-linux.tar.gz# it unpacks into a directory, and the program is inside$ ./chock-x86_64-linux/chock --version$ mv chock-x86_64-linux/chock ~/.local/bin/chock# what holds on this machine$ chock doctor

The archive carries the executable bit, so tar leaves chock ready to run and there is nothing to chmod. A graphical unarchiver can drop it. If the shell answers permission denied, run chmod +x chock and try again.

macOS

There is no macOS file in either channel yet. Build it instead, with the command below. A downloaded build, when there is one, will be unsigned, so macOS will hold it until you clear the quarantine flag with xattr -d com.apple.quarantine.

There is no Intel Mac build. The toolchain can cross compile one. macOS 27 dropped every Intel Mac in September 2026, and the last release that ran on one holds security updates only into 2028. An Intel Mac builds Chock from source, like any platform the workflow skips.

~/src
# every supported platform, from source$ git clone https://github.com/LilithSemi/chock.git$ cd chock$ nix develop --command zig build -Doptimize=ReleaseSmall# then check what this machine can hold$ ./zig-out/bin/chock doctor

What you are running

Chock is pre-alpha, and the status page says what works and what is not built yet. chock doctor reports only the layers it has measured on your machine. A layer that fails to apply fails the tool call. Read the threat model before you point it at anything you care about.