# Install brigade-cli with Homebrew, apt, Nix

Brigade command-line interface. Version 2.6.0 via Homebrew; verified from local package data. Also installable with debian: sudo apt install brig.

## Install

```sh
sudo av install brew:brigade-cli
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install brigade-cli
```

  Evidence: local Homebrew formula metadata

### Linux

- Debian apt (92%):

```sh
sudo apt install brig
```

  Evidence: Debian stable package indexes: brig from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

- Nix (92%):

```sh
nix profile install nixpkgs#brig
```

  Evidence: nixpkgs package indexes: pkgs/by-name/br/brig/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:brigade-cli
- **Package manager:** Homebrew
- **Version:** 2.6.0
- **Source summary:** Brigade command-line interface
- **Homepage:** <https://brigade.sh>
- **Repository:** <https://github.com/brigadecore/brigade>
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- brig (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 2.6.0
## Project history and usage

Brigade CLI, distributed as `brig`, is the command-line client for Brigade, an event-driven scripting platform built on Kubernetes. It belongs to the Kubernetes-native CI/CD and workflow-automation wave of the late 2010s.

### Project history

Brigade's repository was created in October 2017 and early v0.x releases followed in November and December 2017. The project described itself as event-driven scripting for Kubernetes, abstracting cluster details so users could react to events with scripted workflows.

The v2 documentation separates Brigade 2 from legacy Brigade 1.x and documents the `brig` CLI as the route to supported user interactions: login, project initialization, event creation, project management, and log inspection. The README also describes an ecosystem of gateways, event sources, metrics, and SDKs.

By 2022 Brigade had reached v2.6.0, and the CNCF TOC merged a proposal to archive the project in September 2022. The official Brigade docs now carry an archived-project banner while preserving the v2 documentation.

### Adoption history

Brigade had meaningful visibility in the Kubernetes ecosystem, with thousands of GitHub stars and packaging across Homebrew, Debian/Ubuntu, and Nix according to the input package facts. Its adoption was tied to teams experimenting with Kubernetes-native automation before GitHub Actions and other hosted CI systems became dominant defaults.

Current package activity is modest: Homebrew analytics reported low hundreds of installs over the prior year at lookup time, consistent with an archived project that remains packaged for existing users and historical reproducibility.

### How it is used

`brig` is used to log into a Brigade instance, initialize projects, create or manage events, inspect projects, and view worker or job logs. Installation docs offer Homebrew on macOS and direct binary downloads on Linux and Windows.

### Why package nerds care

Brigade CLI is significant because it packages the client side of an ambitious Kubernetes-native automation system. It is also a useful historical marker: a CNCF-era project that reached broad enough distribution for multiple package managers, then moved into archived status while retaining docs and install artifacts.

### Timeline

- 2017: Brigade repository created and early v0.x releases published.
- 2022: v2.6.0 released.
- 2022: CNCF TOC merged the proposal to archive Brigade.
- 2022: Brigade docs updated with archived-project messaging.
- 2026: Homebrew stable version still reported as 2.6.0.

### Related projects

- Brigade gateways include GitHub, Bitbucket, Docker Hub, CloudEvents, and Slack gateway repositories.
- Brigade event sources include cron and other event-producing components.
- Brigade SDKs include Go code in the main repository and a JavaScript/TypeScript SDK referenced by the README.
- Kubernetes is the underlying platform Brigade abstracts.

### Sources

- <https://docs.brigade.sh/topics/project-developers/brig/>
- <https://formulae.brew.sh/api/formula/brigade-cli.json>
- <https://github.com/brigadecore/brigade>
- <https://github.com/cncf/toc/pull/915>
- <https://raw.githubusercontent.com/brigadecore/brigade/main/README.md>


## Security Notes

narrow executable package without higher-risk signals.

- **Geiger risk:** green / low
- narrow executable package without higher-risk signals

## Other Package-Manager Records

- Debian apt - brig - 0.95+dfsg-3: installed executable or alias match | Debian stable package indexes: brig from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | BLAST Ring Image Generator | http://sourceforge.net/projects/brig/
- Nix - brig: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/br/brig/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Ubuntu apt - brig - 0.95+dfsg-3: installed executable or alias match | Ubuntu 24.04 LTS package indexes: brig from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | BLAST Ring Image Generator | http://sourceforge.net/projects/brig/


## Combined YAML source

View the package source record on GitHub. [combined/brigade-cli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/brigade-cli.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
