# git-trim mit Homebrew, Nix installieren

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

## Installation

```sh
sudo av install brew:git-trim
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install git-trim
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#git-trim
```

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

## Paketfakten

- **Paketschlüssel:** brew:git-trim
- **Paketmanager:** Homebrew
- **Version:** 0.4.4
- **Quellzusammenfassung:** Trim your git remote tracking branches that are merged or gone
- **Homepage:** <https://github.com/foriequal0/git-trim>
- **Repository:** <https://github.com/foriequal0/git-trim>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- git-trim (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

git-trim is a Rust Git extension for cleaning local tracking branches whose upstream branches have been merged, deleted, or left behind after pull-request work.

### Projektgeschichte

The project appeared on GitHub in January 2020. Its README frames the tool as a safer companion to git fetch --prune, because fetch pruning removes remote-tracking refs but leaves local tracking branches for the user to inspect and delete.

The project evolved around Git workflow edge cases rather than a large feature surface. Release notes for the 0.4 series describe base-branch detection from remote HEAD refs, worktree branch preservation, richer branch classification, and detailed skip messages.

### Adoptionsgeschichte

Adoption followed normal Git-extension channels: GitHub release binaries, cargo install, Homebrew, and other package-manager formulas. The package fits repositories where pull-request branches accumulate faster than developers want to prune them by hand.

### Wie es verwendet wird

Practitioners run git trim after reviews or after synchronizing a repository. The README recommends dry-run mode for cautious use and trim.bases configuration for workflows with base branches such as develop and master.

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

git-trim matters to package and tooling users because it turns a fragile shell one-liner into a named Git subcommand that understands merged, stray, squash-merged, rebased, and triangular-workflow branches.

### Zeitleiste

- 2020: Repository created and 0.4 releases added workflow-oriented branch detection improvements.
- 2022: v0.4.3 release shipped dependency updates and packaged binaries.

### Related projects

- git fetch --prune, git branch --merged, git2, cargo, Homebrew

### Quellen

- <https://crates.io/crates/git-trim>
- <https://formulae.brew.sh/formula/git-trim>
- <https://github.com/foriequal0/git-trim>
- <https://github.com/foriequal0/git-trim/releases>
- <https://raw.githubusercontent.com/foriequal0/git-trim/master/README.md>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

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

## Andere Paketmanager-Einträge

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


## Quellen

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