# intercept mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für intercept in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:intercept
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install intercept
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:intercept
- **Paketmanager:** Homebrew
- **Version:** 1.0.12
- **Quellzusammenfassung:** Static Application Security Testing (SAST) tool
- **Homepage:** <https://intercept.cc>
- **Repository:** <https://github.com/xfhg/intercept>
- **Zuletzt aktualisiert:** 2026-07-26T04:07:50+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- intercept (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 1.0.12
## Projektgeschichte und Nutzung

INTERCEPT is a small DevSecOps security CLI centered on policy-as-code auditing, SAST-style scanning, compliance reporting, and observe-mode monitoring. Its documentation frames the tool around policy files, audit runs, SARIF output, and an observe daemon for file, service, mount, and configuration drift.

### Projektgeschichte

The GitHub repository was created in March 2020 under `xfhg/intercept`. Public release metadata shows a 1.0 series in 2024 and 2025, with the v1.0.11 notes calling out GitHub Actions integration, compliant output examples, performance optimizations, hooks signatures, auth options, and a remote policy execution endpoint.

### Adoptionsgeschichte

INTERCEPT's adoption footprint is modest and security-specialist oriented. Homebrew packaging gives it a simple macOS/Linux install path, while the official docs and release notes focus on CI, audit output, and policy execution rather than library embedding.

### Wie es verwendet wird

The documented workflow starts from a YAML policy file, then runs `intercept audit` to cycle through loaded policies and produce compliance reports or `intercept observe` to monitor paths and trigger policy audits. The docs describe policy types such as scan, assure, API, JSON, YAML, TOML, INI, runtime, and Rego.

### Warum Paket-Nerds sich dafür interessieren

INTERCEPT is notable less as a large ecosystem and more as a packageable example of the policy-as-code trend entering single-binary CLI tooling. It bundles security scanning, compliance report generation, and daemon-style observation behind a package-manager-installable command.

### Zeitleiste

- 2020: The GitHub repository was created.
- 2024: The v1.0 release series added CI and compliant-output focused features.
- 2025: The v1.0.13 release continued Windows/file-integrity-monitoring work in the 1.0 line.

### Related projects

- INTERCEPT's policy-as-code and Rego support place it near Open Policy Agent workflows, while its SARIF output ties it to GitHub code-scanning and SAST tooling conventions.

### Quellen

- Official repository README, official documentation, GitHub release metadata, GitHub repository metadata, and Homebrew formula metadata.


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## Combined YAML source

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


## Quellen

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