Scut

Usage

Installation

install · release

Install release binaries, pin versions, or build scut from source.

Scut ships as GitHub Release tarballs for macOS and Linux. The install script detects the current platform, downloads the matching artifact, verifies it against checksums.txt, and places the binary on PATH.

Install script

curl -fsSL https://install-scut.ajbeck.dev | sh

The default destination is ~/.local/bin/scut.

Pin a release or choose another directory with installer flags:

curl -fsSL https://install-scut.ajbeck.dev | sh -s -- --version v0.3.3 --bin-dir /usr/local/bin
FlagBehavior
--version VERSIONInstall a specific GitHub Release. The leading v is optional.
--bin-dir DIRInstall scut into the given directory instead of ~/.local/bin.

Updates

Check how the current binary would update before changing anything:

scut update --dry-run

For install-script managed binaries, such as ~/.local/bin/scut, scut update downloads the selected GitHub Release asset, verifies it against checksums.txt, and replaces the current executable:

scut update

Pin a specific release with either positional version syntax or --target-version:

scut update v0.3.4

Homebrew and source-managed installs are not overwritten by scut update. The command prints the appropriate brew or source-build guidance instead.

Release assets

Each stable release publishes one tarball per platform plus a checksum manifest:

scut-v0.3.3-darwin-amd64.tar.gz
scut-v0.3.3-darwin-arm64.tar.gz
scut-v0.3.3-linux-amd64.tar.gz
scut-v0.3.3-linux-arm64.tar.gz
checksums.txt

The tarballs contain one executable named scut.

Source installs

Go users can install from source:

go install github.com/ajbeck/scut@latest

For local development, use Walle so the JSON v2 experiment and build metadata are set consistently:

./walle build

The local binary is written to bin/scut.