Installation

Installation

English · 繁體中文

Package managers

Homebrew, on macOS and Linux:

brew install koukeneko/tap/taiga

Scoop, on Windows:

scoop bucket add koukeneko https://github.com/KoukeNeko/scoop-bucket
scoop install koukeneko/taiga-cli

On Debian/Ubuntu or Fedora/RHEL, install from the signed APT/DNF repository so apt upgrade / dnf upgrade keeps taiga current.

Debian / Ubuntu:

sudo install -d /etc/apt/keyrings
sudo curl -fsSL https://koukeneko.github.io/taiga-cli/taiga-cli.gpg.key -o /etc/apt/keyrings/taiga-cli.gpg.key
echo "deb [signed-by=/etc/apt/keyrings/taiga-cli.gpg.key] https://koukeneko.github.io/taiga-cli/deb stable main" | sudo tee /etc/apt/sources.list.d/taiga-cli.list
sudo apt update && sudo apt install taiga-cli

Fedora / RHEL:

sudo tee /etc/yum.repos.d/taiga-cli.repo >/dev/null <<'EOF'
[taiga-cli]
name=Taiga CLI
baseurl=https://koukeneko.github.io/taiga-cli/rpm
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://koukeneko.github.io/taiga-cli/taiga-cli.gpg.key
EOF
sudo dnf install taiga-cli

The package is named taiga-cli; the command is taiga. Each release also attaches standalone .deb/.rpm for a direct download — see INSTALL.md.

See INSTALL.md for the install scripts, release archives, and upgrade and uninstall commands.

Building from source

Requires Go 1.25 or newer.

make build
./bin/taiga version

Install into ~/.local/bin:

make install

Choose your own location:

make install PREFIX=/usr/local

taiga version reports the version, commit, build time, and platform; add --json for structured output.

Release archives

Downloads, SHA-256 checksum verification, shell completion setup, and upgrade steps for published release archives are documented in INSTALL.md.

Each release ships archives for six platforms, completions for four shells, a SHA256SUMS file, and an SPDX 2.3 SBOM. The same source, Go toolchain, version, commit, and SOURCE_DATE_EPOCH produce byte-identical Linux and Windows archives, so a third party can rebuild and compare independently.

macOS archives are the exception. Their binaries are signed with a Developer ID certificate and notarized by Apple, and notarization requires a secure timestamp, so the signature can never reproduce. Everything else about them is built identically, and a local rebuild without signing configured is reproducible.

macOS Gatekeeper

Released macOS binaries are signed and notarized, so they run without extra steps:

codesign --verify --strict --verbose=2 ./taiga
spctl -a -vvv -t install ./taiga

A notarization ticket cannot be stapled to a bare executable, so Gatekeeper resolves it online. A first run with no network at all can still be blocked; reconnect and run it again, or clear the quarantine attribute with xattr -d com.apple.quarantine ./taiga. Files fetched with curl or wget are never quarantined in the first place.

Rebuilding release artifacts yourself

make release \
  VERSION=v0.1.0 \
  COMMIT="$(git rev-parse HEAD)" \
  SOURCE_DATE_EPOCH="$(git show -s --format=%ct HEAD)"

Output lands in dist/v0.1.0/.

Supported platforms

macOS, Linux, and Windows on amd64 and arm64, all built with CGO_ENABLED=0. Verified Taiga versions and login methods are listed in COMPATIBILITY.md.