Install the CHAMPREP CLI
Choose one installation method. Do not install multiple copies unless you know
which executable appears first in your PATH.
Direct installer for macOS and Linux
Section titled “Direct installer for macOS and Linux”curl -fsSL https://cli.champrep.com/install.sh | shThe installer selects the supported operating system and architecture,
downloads the release from cli.champrep.com, and verifies the published
artifact metadata. The default user installation directory is
$HOME/.local/bin.
Install a specific version or directory with installer options:
curl -fsSL https://cli.champrep.com/install.sh \ | sh -s -- --version VERSION --prefix "$HOME/.local/bin"Review the script at cli.champrep.com/install.sh before running it when required by your security policy.
Homebrew on macOS or Linux
Section titled “Homebrew on macOS or Linux”brew tap champrep-llc/cli \ https://code.champrep.com/champrep-llc/champrep-cli.gitbrew install champrep-llc/cli/champrepUpgrade later with:
brew updatebrew upgrade champrepScoop on Windows
Section titled “Scoop on Windows”scoop bucket add champrep ` https://code.champrep.com/champrep-llc/champrep-cli.gitscoop install champrepUpgrade later with:
scoop update champrepContainer image
Section titled “Container image”docker pull champrep/cli:latestdocker run --rm champrep/cli:latest --versionFor a non-interactive command, inject a scoped key from your secret manager:
docker run --rm \ --env CHAMPREP_TOKEN \ champrep/cli:latest auth whoamiAvoid putting a key directly in a shell command because it can be retained in shell history or process inspection.
Verify the installation
Section titled “Verify the installation”command -v champrepchamprep --versionchamprep versionchamprep --helpIf the command is not found after the direct installer, add the install
directory to PATH and open a new terminal. For example:
export PATH="$HOME/.local/bin:$PATH"Persist the setting in the startup file used by your shell.
Continue
Section titled “Continue”Next, authenticate the CLI. If an older copy is being selected or the binary does not start, use CLI troubleshooting.