Thru CLI

Install the Thru command-line interface with npm:

npm i -g thru     # puts `thru` on your PATH
thru --help

A global install (-g) is what puts the bare thru command on your PATH. A local install works too, but exposes the command through the project instead:

npm i thru        # local dependency
npx thru --help   # or node_modules/.bin/thru

Supported platforms

| platform | arch | binary package | | -------- | ----- | ------------------- | | Linux | x64 | thru-linux-x64 | | Linux | arm64 | thru-linux-arm64 | | macOS | x64 | thru-darwin-x64 | | macOS | arm64 | thru-darwin-arm64 | | Windows | x64 | thru-win32-x64 |

The Linux binaries require glibc >= 2.17, which every mainstream distro since CentOS 7 satisfies (Ubuntu, Debian, RHEL/Rocky/Alma, Amazon Linux, Fedora, SUSE). Alpine/musl is not supported.

Install without npm (Linux packages)

Each release also ships .deb and .rpm packages (x86_64 and aarch64) built from the same binaries, for machines without npm — e.g. cloud VMs. Grab the file for your platform from the releases page and install it directly; no package repository setup is needed:

# Debian / Ubuntu
curl -fsSLO https://github.com/Unto-Labs/thru/releases/download/v0.3.0/thru_0.3.0_amd64.deb
sudo apt install ./thru_0.3.0_amd64.deb

# RHEL / Rocky / Alma / Fedora / Amazon Linux (dnf accepts URLs directly)
sudo dnf install https://github.com/Unto-Labs/thru/releases/download/v0.3.0/thru-0.3.0.x86_64.rpm

Packages installed this way are not picked up by apt upgrade / dnf upgrade (there is no hosted repository); to update, install the newer release's package the same way.

How it works

The thru package contains a small Node.js launcher plus one optionalDependencies entry per platform package above. npm installs only the package whose os/cpu constraints match your machine, and the launcher runs the native binary it carries. Because the binary ships inside a regular npm package:

• no install scripts run — npm install --ignore-scripts works,
• installs work offline or from the npm cache, with npm's usual integrity checks covering the binary itself,
• nothing is downloaded from GitHub at install time.

The same binaries are also published as release assets at https://github.com/Unto-Labs/thru/releases — as plain tarballs (e.g. thru-cli-Linux-x86_64-<tag>.tar.gz) and as the .deb/.rpm packages above, all verified by thru-cli-SHA256SUMS — if you prefer not to use npm.

Troubleshooting

• The thru CLI platform package ... is not installed: the install skipped optional dependencies (--omit=optional / --no-optional). Reinstall without those flags, or download a release binary and set THRU_CLI_BIN.
• THRU_CLI_BIN=/path/to/thru overrides binary resolution entirely; useful for development builds (cargo build in rpc/cli).

Development notes

optionalDependencies are intentionally absent from the committed package.json; scripts/make-platform-packages.mjs generates the platform packages from the built binaries and pins them during the CLI publish workflow (.github/workflows/cli-artifacts.yml). Run node --test for the test suite and node scripts/check-package.mjs for the packaging invariants.