# Install chainloop-cli with Homebrew

CLI for interacting with Chainloop. Version 1.105.3 via Homebrew; verified 2026-08-03.

## Install

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

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install chainloop-cli
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:chainloop-cli
- **Package manager:** Homebrew
- **Version:** 1.105.3
- **Source summary:** CLI for interacting with Chainloop
- **Homepage:** <https://docs.chainloop.dev>
- **Repository:** <https://github.com/chainloop-dev/chainloop>
- **Last updated:** 2026-08-03T03:10:18Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- chainloop (alias)

## Install behavior

- Bottle: not available

## Freshness

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

Chainloop CLI is the developer-facing command-line interface for Chainloop's software supply-chain evidence store and attestation platform. It is used to initialize attestations, add evidence such as SBOMs or vulnerability reports, sign metadata, and push it into Chainloop for validation and storage.

### Project history

Chainloop was introduced on May 22, 2023 as an API for an organization's software supply chain, built around a SLSA level 3 provenance-compliant control plane and a contract-based attestation process. The README describes Chainloop as an open-source evidence store for attestations, SBOMs, VEX, SARIF, QA reports, and related software-delivery evidence.

### Adoption history

The official README and docs emphasize use across CI/CD pipelines, with developers using the CLI while security and compliance teams define workflow contracts, policies, storage, and integrations. Chainloop documentation and changelogs show the platform expanding from attestation capture into policies, compliance frameworks, vulnerability management, integrations, AI coding-session evidence, and enterprise platform features.

### How it is used

The quickstart guides users through installing the CLI, logging in, initializing an attestation, adding a container image, SBOM, and vulnerability report, then pushing the signed attestation. The CLI reference documents commands for applying YAML resources, uploading/downloading artifacts, creating attestations, and passing configuration through ~/.config/chainloop/config.toml or environment variables such as CHAINLOOP_TOKEN.

### Why package nerds care

Package nerds care about chainloop-cli because it is a modern supply-chain CLI that wraps several packaging-era concerns: SBOMs, provenance, signatures, OCI storage, SLSA, in-toto, Sigstore, policy-as-code, and CI/CD evidence capture. Homebrew packaging gives developers a local install path for a tool meant to be embedded in automated delivery pipelines.

### Timeline

- 2023: Chainloop was introduced publicly as an early-access software supply-chain attestation platform.
- 2024: Chainloop changelogs added contract-less attestations, material auto-discovery, broader evidence types, policies, and Prometheus-oriented monitoring.
- 2026: Documentation presents Chainloop as a centralized evidence store with real-time visibility, automated compliance, policy evaluation, and CLI-driven attestation workflows.

### Related projects

- Chainloop is built around or integrates with SLSA, in-toto, Sigstore, OCI registries, OPA/Rego policies, Dependency-Track, GUAC, CycloneDX, SPDX, OpenVEX, SARIF, CSAF, GitHub Actions, GitLab CI, and Kubernetes/Helm deployment paths.

### Sources

- <https://chainloop.dev/blog/introducing-chainloop/>
- <https://github.com/chainloop-dev/chainloop/blob/main/README.md>
- <https://docs.chainloop.dev/welcome.md>
- <https://docs.chainloop.dev/quickstart.md>
- <https://docs.chainloop.dev/command-line-reference/cli-reference.md>
- <https://docs.chainloop.dev/llms.txt>


## Security Notes

No matching local secret-handling manifest was found for chainloop-cli. Nucleus package metadata is still published here so future coverage has a stable package URL.



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ~/.config/chainloop/config.toml

## Credential files

- Unix: ~/.config/chainloop/config.toml

## Combined YAML source

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


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph