<p align="center" <img src="docs/assets/reeve-banner.svg" alt="Reeve" width="440" </p
<p align="center" <strongAudit your AI agents, starting at the endpoint.</strong </p
<p align="center" <a href="https://github.com/Reeve-Security/reeve/actions/workflows/ci.yml"<img src="https://github.com/Reeve-Security/reeve/actions/workflows/ci.yml/badge.svg?branch=main" alt="CI"</a <a href="https://github.com/Reeve-Security/reeve/releases/latest"<img src="https://img.shields.io/github/v/release/Reeve-Security/reeve?sort=semver" alt="Latest release"</a <img src="https://img.shields.io/badge/releases-Sigstore%2FRekor%20signed-2ea44f" alt="Signed releases" <a href="LICENSE"<img src="https://img.shields.io/badge/license-Apache--2.0-blue.svg" alt="License: Apache-2.0"</a </p
AI assistants inherit the authority of the user running them: local files, shells, network paths, saved approvals, and MCP servers wired to internal systems. Reeve reads documented AI-tool config paths, records what is registered, and emits evidence your existing security and compliance tools can verify.
Open source, runs locally. Nothing leaves the endpoint.
- Sees the AI layer. MCP servers, connectors, extensions, the packages
behind them, saved "always allow" approvals, and opt-in secrets in chat logs, across Claude Desktop / Code / Cowork, Cursor, Codex, and other documented surfaces on macOS, Windows, and Linux.
- Speaks standards. A CycloneDX 1.5 SBOM and an AIBOM sidecar on every
scan, with optional Rego policy findings and reports, all in formats your pipeline already ingests.
- Stays local and verifiable. Reads config files by default, never
executes agents unless you opt in, signs its releases with Sigstore, and can sign scan output the same way.
Reeve does not decide safe. It records evidence: what exists, what is granted, what was observed, what a policy flagged. Your patching, MDM, GRC, and review process decide what to do.
Quickstart
Install and run in under a minute. This is the convenience path and it skips signature verification. For production or fleet use, prefer the verified install: see Verify your download.
Linux / macOS. Install script (convenience), or download the release archive:
curl --proto '=https' --tlsv1.2 -LsSf \
https://github.com/Reeve-Security/reeve/releases/latest/download/aibom-cli-installer.sh | shThe install script downloads the binary, verifies it with cosign, and only then installs it. Note this is trust-on-first-use: the script runs before it verifies anything, so piping it to your shell trusts the delivery path (HTTPS and GitHub release integrity) for that first step. For production or fleet rollouts, use the verified install below instead of piping to a shell.
Prefer not to pipe a script to your shell? Download the .tar.xz archive from the latest release and extract aibom-cli.