> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/setup-apps-os/cli-in-cicd/installing-the-cli.md).

# Installing the Seal CLI

The Seal CLI is published as a single binary per platform. There is no installer-managed package today; you download the binary, place it on the `PATH`, and run it. Seal's releases are at [`github.com/seal-community/cli/releases`](https://github.com/seal-community/cli/releases).

In CI/CD pipelines, the install is a step in the pipeline itself. See the per-platform integration pages ([GitHub Actions](/setup-apps-os/cli-in-cicd/github-actions.md), [GitLab CI](/setup-apps-os/cli-in-cicd/gitlab-ci.md), [Azure DevOps](/setup-apps-os/cli-in-cicd/azure-devops.md), [Jenkins](/setup-apps-os/cli-in-cicd/jenkins.md), [CircleCI](/setup-apps-os/cli-in-cicd/circleci.md), [Dockerfile](/setup-apps-os/cli-in-cicd/dockerfile.md)) for the exact shape of that step on your platform.

## Linux

```bash
curl -fsSL https://github.com/seal-community/cli/releases/download/latest/seal-linux-amd64-latest.zip -o seal.zip
unzip seal.zip
chmod +x seal
./seal version
```

The downloaded archive contains the `seal` binary. Place it on the `PATH` (for example, `mv seal /usr/local/bin/seal`) for system-wide use, or run it from the working directory as shown.

## macOS

A signed `.pkg` installer is available from the [latest release](https://github.com/seal-community/cli/releases/tag/latest). Download it and double-click to install; the binary lands at `/usr/local/bin/seal`.

A zipped binary is also available on the same release page if you prefer to install manually:

```bash
curl -fsSL https://github.com/seal-community/cli/releases/download/latest/seal-darwin-amd64-latest.zip -o seal.zip
unzip seal.zip
chmod +x seal
./seal version
```

For Apple Silicon, swap `amd64` for `arm64` in the URL.

## Windows

The Windows binary is `amd64` (x86-64), published as both a `.zip` and a standalone `seal-windows-amd64-latest.exe` on the [latest release](https://github.com/seal-community/cli/releases/tag/latest).

```powershell
Invoke-WebRequest -Uri https://github.com/seal-community/cli/releases/download/latest/seal-windows-amd64-latest.zip -OutFile seal.zip
Expand-Archive seal.zip -DestinationPath .
.\seal.exe version
```

The archive contains the `seal.exe` binary. Run it from the working directory as shown, or add its directory to the `Path` environment variable for use anywhere.

{% hint style="info" %}
The Windows binary is unsigned, so Windows SmartScreen may warn on first run. The `gradle` and `bundler` package managers are not yet supported on Windows; running the CLI against a Gradle or Bundler project on Windows prints a "not yet supported on Windows" message. The other supported package managers behave as they do on Linux and macOS.
{% endhint %}

## Verifying the install

```bash
seal version
```

The command prints the installed version. If the output is a version string, the install is good.

## Use the latest version

For new installs, use `latest`. The Seal CLI deprecates older versions over time, so a build that pins an old version eventually stops working as the platform moves forward. The recommended practice is to use whatever the `latest` URL resolves to, and to refresh the install whenever the CLI changes underneath your build.

If you have a strong operational reason to pin (a regulated environment with a frozen build chain, for example), pin to a recent version and treat the pin as a renewal commitment: keep the pinned version no more than six months old, and upgrade on a regular cadence.

## Related

* [The CLI fix mode](/setup-apps-os/cli-in-cicd/cli-fix-mode.md): what to pass next, once the CLI is on the `PATH`.
* [Network requirements](/reference/network-requirements.md): the hostnames the CLI host needs reachable.
* The per-platform CI integration pages for pipeline-step shapes.