# Installer intercept avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de intercept pour les workflows d'agents IA.

## installation

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

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install intercept
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:intercept
- **Gestionnaire de paquets:** Homebrew
- **Version:** 1.0.12
- **Résumé source:** Static Application Security Testing (SAST) tool
- **Page d'accueil:** <https://intercept.cc>
- **Dépôt:** <https://github.com/xfhg/intercept>
- **Dernière mise à jour:** 2026-07-26T04:07:50+02:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- intercept (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 1.0.12
## Historique du projet et usages

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.

### Historique du projet

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.

### Historique d'adoption

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.

### Modes d'utilisation

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.

### Pourquoi les passionnés de paquets s'y intéressent

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.

### Chronologie

- 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.

### Sources

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


## Notes de sécurité

narrow executable package without higher-risk signals.

- **Risque Geiger:** vert / faible
- 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)


## Sources

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