# checkov mit Homebrew, Nix installieren

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

## Installation

```sh
sudo av install brew:checkov
```

## Antwort zur Agent-Sicherheit

checkov scans infrastructure code and may read sensitive templates and policy context.

- **Credential-Zugriff:** Reads IaC files, environment variables, and optional platform tokens.
- **Änderungen an Remote-Zustand:** Usually read-only, but integrations can report to remote services.
- **Publish-/Artefakt-Risiko:** Can produce security reports that may include resource names and paths.
- **Empfohlene Kontrolle:** Gate token-backed uploads and scans over secret-bearing files.
- **Hinweise für Agent-Nutzung:** Allow local scans; require approval before uploading findings or scanning sensitive directories.

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install checkov
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#checkov
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/ch/checkov/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:checkov
- **Paketmanager:** Homebrew
- **Version:** 3.3.0
- **Quellzusammenfassung:** Prevent cloud misconfigurations during build-time for IaC tools
- **Homepage:** <https://www.checkov.io/>
- **Zuletzt aktualisiert:** 2026-07-25T10:24:22Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- checkov (Alias)
- checkov.cmd (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

Checkov is an infrastructure-as-code static analysis tool created by Bridgecrew and maintained under Prisma Cloud. It became a major security package because it brought policy-as-code checks for Terraform, Kubernetes, CloudFormation, Dockerfiles, CI workflows, and related formats into a single installable CLI.

### Projektgeschichte

The bridgecrewio/checkov repository was created in November 2019. The official README describes Checkov as a static code analysis tool for IaC and software composition analysis, maintained by Prisma Cloud and able to detect cloud misconfigurations and vulnerabilities during build time.

Checkov expanded from Terraform-oriented misconfiguration scanning into a broader scanner for Terraform plans, CloudFormation, AWS SAM, Kubernetes, Helm, Kustomize, Dockerfiles, Serverless, Bicep, ARM templates, OpenAPI, OpenTofu, CI pipelines, container images, and open source packages.

### Adoptionsgeschichte

Checkov was first uploaded to PyPI in December 2019 and was still publishing frequent 3.x releases in June 2026. The official README documents installation through pip, Homebrew, Docker, and upgrades through pip or brew.

Docker Hub metadata for bridgecrew/checkov showed more than 22 million pulls by June 2026, and the GitHub repository metadata showed thousands of stars, indicating adoption well beyond niche use. In 2021, Palo Alto Networks announced completion of its Bridgecrew acquisition, after which the README and docs positioned Checkov as part of Prisma Cloud Application Security.

### Wie es verwendet wird

Typical CLI usage scans a directory, file, or Terraform plan JSON and emits findings with policy IDs, file paths, pass/fail status, and remediation links. Output formats include CLI, CycloneDX, JSON, JUnit XML, CSV, SARIF, and GitHub markdown.

Teams commonly run Checkov locally, in CI, or in pull request workflows to block insecure infrastructure definitions before deployment. With a Prisma Cloud API key, the CLI can also use severity thresholds and platform-backed policy metadata.

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

Checkov is package-nerd significant because it is a high-churn Python security CLI with multiple distribution channels, a large policy corpus, Docker images, Homebrew packaging, PyPI releases, and enterprise integration pressure. It shows how cloud-security tooling moved from SaaS dashboards into developer workstation and CI packages.

Its packaging story also reflects IaC's growth: a single command-line package became a front door for scanning Terraform, Kubernetes, Docker, CI configuration, secrets, and SCA inputs.

### Zeitleiste

- 2019: bridgecrewio/checkov repository created and first PyPI release uploaded.
- 2021: Palo Alto Networks completed its acquisition of Bridgecrew.
- 2026: Checkov 3.3.x releases published and Docker image updated.

### Related projects

- Prisma Cloud Application Security is the commercial platform integration documented by Checkov.
- Terraform, OpenTofu, Kubernetes, CloudFormation, Helm, Docker, CycloneDX, and SARIF are major adjacent ecosystems and formats supported by Checkov.

### Quellen

- <https://github.com/bridgecrewio/checkov>
- <https://www.checkov.io/>
- <https://github.com/bridgecrewio/checkov/releases>
- <https://pypi.org/project/checkov/>
- <https://hub.docker.com/r/bridgecrew/checkov>
- <https://www.paloaltonetworks.com/company/press/2021/palo-alto-networks-completes-acquisition-of-bridgecrew>


## Sicherheitshinweise

infrastructure mutation or orchestration signal.

- **Geiger-Risiko:** orange / mittel
- infrastructure mutation or orchestration signal


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


## Credential files

- Unix: ~/.bridgecrew/credentials
## Andere Paketmanager-Einträge

- Nix - checkov: normalized package name match | nixpkgs package indexes: pkgs/by-name/ch/checkov/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

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


## Quellen

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