Skip to content

Install & verify

murk ships as a single binary with no runtime dependencies.

Terminal window
brew install interrupted-sh/tap/murk

Installing by the full name trusts only the murk formula, not every formula in the tap (Homebrew tap trust). Tap trust and brew trust need Homebrew 6.0 or later.

Upgrading from the old tap name. The tap used to be interrupted-sh/murk. You don’t need to untap or reinstall: brew update follows the rename and moves your tap to interrupted-sh/tap. Trust doesn’t follow a rename, so trust the formula under its new name once, then upgrade:

Terminal window
brew update
brew trust --formula interrupted-sh/tap/murk
brew upgrade murk

Requires the Rust toolchain, Rust 1.89 or later:

Terminal window
cargo install murk-cli

Downloads a pre-built binary for Linux or macOS:

Terminal window
curl -fsSL https://raw.githubusercontent.com/interrupted-sh/murk/main/install.sh | sh

The script checks the archive against the release’s SHA256SUMS. That catches a corrupt download but not a tampered release. The script then checks the release’s build provenance with the GitHub CLI (gh, logged in with gh auth login or GH_TOKEN). If a check fails, the install stops.

If gh is missing or not logged in, the script asks whether to install anyway (default no). Without a terminal, as in CI or a docker build, it stops unless MURK_SKIP_ATTESTATION=1 is set for sh. Set MURK_TAG=v0.15.1 to install a specific release.

The script installs to /usr/local/bin/murk by default. It uses sudo only when that directory is not writable. To install somewhere else, set these variables:

  • PREFIX sets the installation prefix (default /usr/local). The binary goes to $PREFIX/bin.
  • DESTDIR is prepended to the final path for staged installs, as with make install: DESTDIR=/tmp/stage PREFIX=/usr writes /tmp/stage/usr/bin/murk.
  • MURK_INSTALL_DIR names the exact bin directory and takes precedence over PREFIX. DESTDIR still applies on top of it.

Set the variables just before sh, not before curl. In a pipe, a variable set before curl reaches only curl, and the script never sees it:

Terminal window
curl -fsSL https://raw.githubusercontent.com/interrupted-sh/murk/main/install.sh | PREFIX="$HOME/.local" sh

murk provides pre-built binaries for Linux (x86_64, aarch64, armhf), macOS (x86_64, Apple Silicon), and Windows on the releases page.

Download the archive for your platform. Each one is named murk-v<version>-<target>, for example murk-v0.15.1-aarch64-apple-darwin.tar.gz. Linux and macOS archives are .tar.gz files. The Windows archive (x86_64-pc-windows-msvc) is a .zip. Verify the download, then extract it and put the binary in a directory on your PATH:

Terminal window
tar xzf murk-v0.15.1-aarch64-apple-darwin.tar.gz
sudo mv murk /usr/local/bin/

On Windows, extract murk.exe from the .zip into a folder on your PATH.

@interrupted/murk-secrets on npm and murk-secrets on PyPI let a program read a vault from code. The Node package can also store secrets. Neither package includes the murk command. Install the CLI first and use it to create the vault. See Library bindings.

Binary releases carry signed build provenance (actions/attest-build-provenance, backed by Sigstore/Fulcio). Verify a downloaded artifact with the GitHub CLI:

Terminal window
gh attestation verify murk-v0.15.1-aarch64-apple-darwin.tar.gz \
--repo interrupted-sh/murk \
--signer-workflow interrupted-sh/murk/.github/workflows/release.yaml \
--source-ref refs/tags/v0.15.1

File names include the tag with its v. The Windows file is a .zip. This checks that the release workflow in this repository built the file from that tag. Without --source-ref, an older genuine archive renamed to a newer release name would still pass. gh must be logged in (gh auth login). The same check works for SHA256SUMS.

Releases 0.11.0 and earlier name an older repository in their provenance (interrupted-inc/murk or iicky/murk). See Verifying releases for the commands that verify them.

The npm, PyPI and crates.io packages are verified differently: npm provenance for the npm package, PEP 740 attestations for PyPI, and an attested .crate for crates.io (0.13.0 and later). Release tags are SSH-signed. Verifying releases covers each channel and where to get the tag-signing key.

Once murk is installed, follow the quick start to join an existing project, or start a new vault.