# 使用 Homebrew 安装 chainloop-cli 查看 chainloop-cli 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。 ## 安装 ```sh sudo av install brew:chainloop-cli ``` 其他安装命令: ### macOS - Homebrew (100%): ```sh brew install chainloop-cli ``` 证据: local Homebrew formula metadata ## 软件包事实 - **软件包键:** brew:chainloop-cli - **软件包管理器:** Homebrew - **版本:** 1.105.3 - **来源摘要:** CLI for interacting with Chainloop - **主页:** - **仓库:** - **最后更新:** 2026-08-03T03:10:18Z - **已生成:** 2026-08-03T19:37:03+00:00 ## 可执行文件 - chainloop (别名) ## 安装行为 - Bottle: 不可用 ## 版本和新鲜度 - 页面生成时间: 2026-08-03 - 管理器版本: 1.105.3 ## 项目历史与用法 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. ### 项目历史 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. ### 采用历史 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. ### 使用方式 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. ### 为什么软件包爱好者会关心 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. ### 时间线 - 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. ### 来源 - - - - - - ## 安全说明 没有找到 chainloop-cli 的匹配本地密钥处理 manifest。Nucleus 软件包元数据仍在此发布，以便未来覆盖拥有稳定的软件包 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) ## 来源 - 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