Automic VaultAutomic Vault

brew

gtrash mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install gtrash

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#gtrash

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

Überblick

Paketzusammenfassung

Featureful Trash CLI manager: alternative to rm and trash-cli

Befehle und Aliase

  • gtrash

Verlauf

Projektgeschichte und Nutzung

gtrash is a Go command-line trash manager built as a safer shell-facing alternative to permanent removal with rm. Its identity is tied to the FreeDesktop.org trash specification: on Linux it writes the same trash metadata and files layout used by desktop environments and other compliant CLI tools, while also offering a TUI-oriented recovery workflow.

Projektgeschichte

The public repository was created in January 2024, with its initial commit dated 2024-01-06 and a v0.0.1 release published on 2024-01-08. The README presents the project as a featureful trash CLI manager that can substitute for common rm habits while keeping files recoverable.

The design focuses on a single static Go binary with multiple subcommands. The core operation moves files into a trash location and records .trashinfo metadata, while companion commands list, restore, remove, summarize, and repair trash entries.

Adoptionsgeschichte

gtrash entered package-manager culture as a small modern CLI rather than as a long-lived Unix base tool. The official README documents installation paths through binary releases, Go install, Nixpkgs, Homebrew, and AUR-style packages; the input metadata also records Homebrew and Nix packaging.

Wie es verwendet wird

The everyday use case is replacing direct deletion with `gtrash put`, then using `gtrash find`, `gtrash restore`, `gtrash restore-group`, `gtrash summary`, or permanent removal options when cleanup is intentional. On Linux, normal trash entries live under `$XDG_DATA_HOME/Trash` or `$HOME/.local/share/Trash`, with external filesystems handled through `.Trash/$uid` or `.Trash-$uid` locations.

The README explicitly warns against blindly aliasing `rm=gtrash put`, because sudo, SSH hosts, and partial rm compatibility can surprise users. That caution is part of the tool's package-nerd appeal: it is safer than rm, but honest about Unix muscle memory.

Warum Paket-Nerds sich dafür interessieren

gtrash matters to package users who want a Freedesktop-compatible trash CLI with Go-style distribution ergonomics. It overlaps with `gio trash` and `trash-cli`, but emphasizes a modern TUI, grouped restoration, static binaries, and rm-like flags without inventing a private trash format.

Zeitleiste

  • 2024-01-06: Public repository initial commit.
  • 2024-01-08: v0.0.1 release published.
  • 2024: README documents package-manager installation through Go install, Nixpkgs, Homebrew, and AUR-style packages.
  • 2025: Repository metadata shows continued maintenance activity into 2025.

Related projects

  • The README positions gtrash alongside `rm`, `gio trash`, `trash-cli`, and `rip`. Its technical foundation is the FreeDesktop.org trash specification, so it is most related to tools and desktops that share that on-disk trash layout.

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.
  • 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
gtrashcliglobales 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.0.6
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.0.6

https://github.com/umlx5h/gtrash

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:gtrash
Version0.0.6
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/gtrash
Homepagehttps://github.com/umlx5h/gtrash
Repositoryhttps://github.com/umlx5h/gtrash
Upstream-Dokumentationhttps://github.com/umlx5h/gtrash#readme
LizenzMIT
Quellarchivhttps://github.com/umlx5h/gtrash/archive/refs/tags/v0.0.6.tar.gz
Build-Abhängigkeitengo
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 Namegtrash
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Nix95%

gtrash

nix profile install nixpkgs#gtrash
  • normalized package name match
  • Abgeglichen nach: Gtrash
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/gt/gtrash/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