# ktfmt mit Homebrew, Nix installieren

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

## Installation

```sh
sudo av install brew:ktfmt
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install ktfmt
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#ktfmt
```

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

## Paketfakten

- **Paketschlüssel:** brew:ktfmt
- **Paketmanager:** Homebrew
- **Version:** 0.64
- **Quellzusammenfassung:** Kotlin code formatter
- **Homepage:** <https://facebook.github.io/ktfmt/>
- **Repository:** <https://github.com/facebook/ktfmt>
- **Zuletzt aktualisiert:** 2026-06-24T03:35:16Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- ktfmt (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

ktfmt is Meta's Kotlin formatter, built to pretty-print Kotlin code deterministically and with minimal style choice. The project describes itself as based on google-java-format and intentionally non-customizable to promote consistency.

### Projektgeschichte

The repository README describes ktfmt as a formatter that reformats Kotlin source code and compares its output with ktlint and IntelliJ formatting. Its website emphasizes that the same input always receives the same output, regardless of initial layout, so developers can avoid style debates.

### Adoptionsgeschichte

ktfmt is consumed both as a command-line jar and through integrations: a JetBrains IDE plugin, Gradle and Maven examples, Spotless integration, Maven Central artifacts, and Homebrew packaging. That puts it in the same culture as gofmt and google-java-format, where a formatter's value is partly social: teams agree to stop arguing about layout.

### Wie es verwendet wird

Users run ktfmt from the command line, through build tooling, through Spotless, or through the IntelliJ and Android Studio plugin. The README documents editorconfig use for approximating ktfmt behavior in IDE editing and command-line options for whole-file or partial formatting.

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

ktfmt matters to package people because it packages style as an executable policy. It is a Kotlin example of formatter distribution via Maven Central, IDE plugins, build plugins, jars, and Homebrew, with very little configuration surface by design.

### Zeitleiste

- 2024-10-30: The v0.53 tag was published in the GitHub tag history.
- 2025-06-25: The v0.56 tag was published in the GitHub tag history.
- 2026-03-17: The v0.62 tag was published in the GitHub tag history.
- 2026-06-24: Release 0.64 was published on GitHub.

### Related projects

- Related projects include google-java-format, ktlint, IntelliJ IDEA formatting, Android Studio, Spotless, Gradle, Maven, and Kotlin coding conventions.

### Quellen

- <https://facebook.github.io/ktfmt/>
- <https://github.com/facebook/ktfmt>
- <https://github.com/facebook/ktfmt/releases>
- <https://github.com/facebook/ktfmt/tags>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

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


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


## Configuration files

- Unix: .editorconfig
## Andere Paketmanager-Einträge

- Nix - ktfmt: normalized package name match | nixpkgs package indexes: pkgs/by-name/kt/ktfmt/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/ktfmt.yml](https://github.com/mxcl/pkgdb/blob/main/combined/ktfmt.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