Automic VaultAutomic Vault

brew

cfripper mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install cfripper

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#cfripper

nixpkgs package indexes · pkgs/by-name/cf/cfripper/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Library and CLI tool to analyse CloudFormation templates for security issues

Verlauf

Projektgeschichte und Nutzung

CFRipper is a Skyscanner library and CLI for analyzing AWS CloudFormation templates for security and compliance issues. The official README describes it as a way to prevent deploying insecure AWS resources and to add custom compliance plugins.

Projektgeschichte

The official GitHub repository was created in July 2018. Its documentation presents CFRipper as both a library and command-line analyzer, with examples for scanning CloudFormation YAML or JSON templates, resolving references, emitting text or JSON output, and loading custom rule configuration.

The project sits in the CloudFormation security-analysis niche rather than the general linting niche: its examples focus on wildcard principals, overprivileged IAM roles, monitored issues, and compliance rule customization.

Adoptionsgeschichte

Official documentation is published on Read the Docs, the README advertises PyPI and Homebrew badges, and the package metadata in this batch shows Homebrew and Nix packaging.

CFRipper's adoption is tied to security review workflows for CloudFormation templates: it is useful before deployment, in CI, or as a library embedded in custom cloud-governance checks.

Wie es verwendet wird

The README documents running `cfripper` against one or more CloudFormation templates, choosing `txt` or `json` output, using `--resolve`, writing results with `--output-folder`, and passing custom rules config or rules filter folders.

The official docs show rules config files as command inputs rather than a fixed application config location, so `config-file-location` remains null. No official credential file location is documented for the CLI.

Warum Paket-Nerds sich dafür interessieren

CFRipper is notable because it packages cloud-security review into an ordinary CLI: a repository can add it to pre-deploy checks without first building an internal CloudFormation parser and IAM rule engine.

It also shows the common packaging path for Python security tools: library plus CLI, PyPI first, then Homebrew or Nix for operators who want a standalone command.

Zeitleiste

  • 2018: The Skyscanner/cfripper repository is created on GitHub.
  • 2018: The project documents CloudFormation security analysis and custom compliance plugins.
  • 2026: The repository and Read the Docs site remain the official documentation surfaces.

Related projects

  • AWS CloudFormation templates are the artifacts CFRipper analyzes.
  • IAM policy and principal rules are central to the README examples.
  • cfn-lint is an adjacent CloudFormation validation tool, while CFRipper focuses on security and compliance rules.

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • infrastructure mutation or orchestration signal

Signale

  • text:cloud

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 3 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
cfrippercliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version1.21.0
Manager aktualisiert2026-07-01
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://cfripper.readthedocs.io

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:cfripper
Version1.21.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/cfripper
Homepagehttps://cfripper.readthedocs.io
Repositoryhttps://github.com/Skyscanner/cfripper
Upstream-Dokumentationhttps://cfripper.readthedocs.io/
LizenzApache-2.0
Quellarchivhttps://files.pythonhosted.org/packages/0c/6b/ae7ef7f1984222dd5a93cf53cdda8f802cf9c3e0855f671dcb15b3a2a89a/cfripper-1.21.0.tar.gz
Zuletzt aktualisiert2026-07-01T15:27:38Z
Pulseupdated
Abhängigkeitenlibyaml, pydantic, python@3.14
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namecfripper
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

cfripper

nix profile install nixpkgs#cfripper
  • normalized package name match
  • Abgeglichen nach: Cfripper
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/cf/cfripper/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment