Install gnux.
One static binary carries all 108 tools, with no runtime and nothing else to install. Put it on your machine, link the tool names to it, and each one is a command of its own.
01macOS
3 steps
macOS: A Homebrew cask, with shell completion for bash, zsh and fish.
Terminal
Number 01
Step 1: Install
The gnux repository is its own Homebrew tap; the cask installs the gnux binary and its completions.
Terminal brew tap braswelljr/gnux https://github.com/braswelljr/gnux brew install --cask braswelljr/gnux/gnuxTerminal
Number 02
Step 2: Link the tool names
gnux picks the tool from the name it was started under, so each name linked to the binary is a command of its own: rmx, cpx, lsx and the rest.
Terminal bin="$(dirname "$(command -v gnux)")" for t in $(gnux --list); do ln -sf gnux "$bin/$t"; doneTerminal
Number 03
Step 3: Check
Every tool answers to --version; the second line should list the current directory.
Terminal rmx --version lsx -la
The cask always installs the newest release. For one particular version, use Go (go install github.com/braswelljr/gnux@v1.4.0) or a release archive.
02Windows
3 steps
Windows: winget or Scoop, then hard links: no WSL, no admin rights, no extra disk space.
PowerShell
Number 01
Step 1: Install
Either package manager installs the native, statically linked gnux.exe.
PowerShell winget install braswelljr.gnux # or scoop bucket add gnux https://github.com/braswelljr/gnux scoop install gnux/gnuxPowerShell
Number 02
Step 2: Link the tool names
gnux picks the tool from the name it was started under, so each name linked to the binary is a command of its own: rmx, cpx, lsx and the rest.
PowerShell $bin = Split-Path (Get-Command gnux).Source foreach ($t in gnux --list) { Remove-Item "$bin\$t.exe" -ErrorAction SilentlyContinue New-Item -ItemType HardLink -Path "$bin\$t.exe" -Target "$bin\gnux.exe" | Out-Null }PowerShell
Number 03
Step 3: Check
Open a new PowerShell window so it sees the new names, then run a tool.
PowerShell rmx --version lsx -la
Hard links need neither Developer Mode nor elevation. Copying gnux.exe to each name also works, at the cost of disk space; rerun either loop after an upgrade. For one particular version: winget install braswelljr.gnux --version 1.4.0, or scoop install gnux/gnux@1.4.0.
03Linux and FreeBSD
4 steps
Linux and FreeBSD: A package for your distribution or a release archive, checked against its checksums, for amd64, arm64 or riscv64.
Shell
Number 01
Step 1: Download and verify
Pick the archive for your platform from the releases page; the checksum file proves it arrived intact.
Shell v=v1.4.0 curl -LO "https://github.com/braswelljr/gnux/releases/download/$v/gnux-$v-linux-amd64.tar.gz" curl -LO "https://github.com/braswelljr/gnux/releases/download/$v/checksums.txt" sha256sum --check --ignore-missing checksums.txtShell
Number 02
Step 2: Install
One static binary: no dependencies to install with it.
Shell tar -xzf "gnux-$v-linux-amd64.tar.gz" sudo mv "gnux-$v-linux-amd64/gnux" /usr/local/bin/Shell
Number 03
Step 3: Link the tool names
gnux picks the tool from the name it was started under, so each name linked to the binary is a command of its own: rmx, cpx, lsx and the rest.
Shell bin="$(dirname "$(command -v gnux)")" for t in $(gnux --list); do sudo ln -sf gnux "$bin/$t"; doneShell
Number 04
Step 4: Check
Every tool answers to --version.
Shell rmx --version lsx -la
Every release also carries a .deb, an .rpm and an .apk under the same name (sudo dpkg -i "gnux-$v-linux-amd64.deb"), and is published as a snap (sudo snap install gnux, confined to your home directory), on the AUR (gnux-bin) and as a Homebrew cask (the macOS steps work on Linux too). Set v to any tag to install that version.
04Any platform, with Go
3 steps
Any platform, with Go: Builds the latest version from source with the Go toolchain, 1.26 or newer; name a tag instead of latest (@v1.4.0) for that version.
Shell
Number 01
Step 1: Install
The binary lands in $(go env GOPATH)/bin, which should be on your PATH.
Shell go install github.com/braswelljr/gnux@latestShell
Number 02
Step 2: Link the tool names
gnux picks the tool from the name it was started under, so each name linked to the binary is a command of its own: rmx, cpx, lsx and the rest.
Shell bin="$(dirname "$(command -v gnux)")" for t in $(gnux --list); do ln -sf gnux "$bin/$t"; doneShell
Number 03
Step 3: Check
Every tool answers to --version.
Shell rmx --version lsx -la
05GitHub Actions
1 step
GitHub Actions: The setup-gnux action: the same tools on Linux, macOS and Windows runners.
.github/workflows/ci.yml
Number 01
Step 1: Add the action
It installs a verified release and puts gnux and every tool name on PATH, so later steps just use them.
.github/workflows/ci.yml - uses: braswelljr/gnux@v0 with: version: latest - run: rmx -rf build && mkdirx -p build && cpx -r assets build/
Set gnu-names: true to also link rm, cp, ls and the rest ahead of the runner’s own tools.
06Docker
2 steps
Docker: Build the image from a checkout and mount the directory to work on.
Shell
Number 01
Step 1: Build
The image carries gnux and every tool name.
Shell git clone https://github.com/braswelljr/gnux && cd gnux docker build -t gnux .Shell
Number 02
Step 2: Run
Mount the current directory at /work, where the tools start.
Shell docker run --rm -v "$(pwd):/work" gnux lsx -la docker run --rm -v "$(pwd):/work" --entrypoint rmx gnux -rv build/
07Next
Installed. Now what?
The getting started guide walks through your first commands, the GNU-name aliases and shell completion. Or try any tool in the browser first.