Automic VaultAutomic Vault

brew

cfr-decompiler mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install cfr-decompiler

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Yet Another Java Decompiler

Befehle und Aliase

  • cfr-decompiler

Verlauf

Projektgeschichte und Nutzung

CFR is a Java bytecode decompiler distributed as the `cfr-decompiler` Homebrew formula. Its official site describes it as another Java decompiler that can handle modern Java features while being written in Java 6 for broad runtime compatibility.

Projektgeschichte

The official GitHub repository was created in May 2014 and points users to benf.org as the main CFR site. The README says CFR can decompile modern Java features, including Java 9, 12, and 14 features, and can make a reasonable attempt at JVM languages such as Kotlin, Scala, and Groovy.

The benf.org project page records a long release history, including 0.146 in July 2019, 0.147 in October 2019, 0.150 in May 2020, 0.151 in February 2021, and 0.152 in December 2021. The README notes that since 0.145, binaries have also been published on GitHub releases.

Adoptionsgeschichte

CFR's adoption comes from the Java reverse-engineering and debugging niche: developers use it when they need readable Java-like output from class files or jars, especially for newer language features that older decompilers may not handle cleanly.

Official distribution includes the benf.org jar downloads, GitHub release artifacts, and Maven Central. The Homebrew package wraps that Java tool in a package-manager-friendly executable for macOS users.

Wie es verwendet wird

The documented use is to run the versioned jar against class names or class files, or pass an entire jar and an `--outputdir` when emitting files. The README also documents `--help` for arguments.

CFR supports an options file for decompilation tests, but the official user docs do not document a persistent application config path or credential file for normal CLI use, so both locations are null.

Warum Paket-Nerds sich dafür interessieren

CFR matters to package people because decompilers are operational tools as much as developer tools: they are installed when source is missing, artifacts are suspicious, or bytecode behavior needs inspection.

It is also a classic example of a small Java jar that package managers wrap into a named executable. The package value is not dependency complexity; it is putting a known decompiler on PATH.

Zeitleiste

  • 2014: The leibnitz27/cfr public repository is created on GitHub.
  • 2019: CFR 0.146 and 0.147 add support and fixes for Java and Kotlin bytecode patterns.
  • 2021: CFR 0.152 is published on benf.org with support and fixes for newer Java features including sealed classes.
  • 2026: The official site notes renewed tinkering and points users to the GitHub repository for a modern version.

Related projects

  • The Java compiler and JVM class-file format are the direct targets CFR decompiles.
  • Kotlin, Scala, and Groovy are named in the README as JVM languages whose class files CFR may attempt to turn back into Java.
  • Maven Central is an official distribution channel for CFR artifacts.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 1 Build-Abhä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
cfr-decompilercliglobales 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-Version0.152
Manager aktualisiert2026-06-22
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/leibnitz27/cfr

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:cfr-decompiler
Version0.152
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/cfr-decompiler
Homepagehttps://www.benf.org/other/cfr/
Repositoryhttps://github.com/leibnitz27/cfr
Upstream-Dokumentationhttps://github.com/leibnitz27/cfr#readme
LizenzMIT
Quellarchivhttps://github.com/leibnitz27/cfr.git
Zuletzt aktualisiert2026-06-22T14:03:00-07:00
Pulseupdated
Abhängigkeitenopenjdk@21
Build-Abhängigkeitenmaven
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 Namecfr-decompiler
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

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
  • package relationship graph
  • package version freshness
  • package-page enrichment