Automic VaultAutomic Vault

brew

git-spice mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install git-spice

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#git-spice

nixpkgs package indexes · pkgs/by-name/gi/git-spice/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Manage stacked Git branches

Befehle und Aliase

  • git-spice

Verlauf

Projektgeschichte und Nutzung

git-spice is a Git stacking tool that manages dependent branches and submits them as pull requests or merge requests across several forge providers.

Projektgeschichte

The project repository was created in 2023, with early public code and alpha tags appearing in 2024. Its documentation defines stacking as creating branches or change requests that build on top of each other so related work can stay small and reviewable while preserving dependency order.

git-spice grew from local branch navigation and restacking into a forge-aware workflow tool. The README and documentation describe support for GitHub, GitLab, Bitbucket, Gitea, Forgejo, and Codeberg-style workflows, while the changelog records later additions such as fork-based contribution flows, Ubuntu PPA packaging, and experimental stack merge commands.

Adoptionsgeschichte

Adoption belongs to the stacked-PR niche, a workflow popular among engineers who split large changes into reviewable layers. The project documents incremental adoption, offline-first local state, shorthand commands, and a visible user-community section, making it part of the newer wave of Git tools that bring Phabricator-style stacked change review to GitHub and GitLab users.

Wie es verwendet wird

Practitioners use git-spice through the git-spice executable or the gs shorthand. Typical flows create or track stacked branches, submit one branch or an entire stack, sync with trunk, delete merged branches, restack dependent branches after base changes, and keep local metadata in Git configuration.

Warum Paket-Nerds sich dafür interessieren

git-spice matters to package and developer-tool watchers because it is a forge-neutral, open-source entry in the stacked-branch space. Its packaging in Homebrew and Nix makes a workflow that once depended on hosted services or workplace-specific tooling easier to install as a normal CLI.

Zeitleiste

  • 2023: GitHub repository was created.
  • 2024: First public code and alpha tags appeared.
  • 2026: Changelog entries documented fork workflows, additional forge support, and stack merge experiments.

Related projects

  • The related practice area is stacked pull requests and merge requests, with git-spice positioning itself as a Git-compatible branch manager rather than a replacement for Git.

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.

local files

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

Config paths the tool may read or write during local use.

Unix
.git/config~/.gitconfig~/.config/git/config/etc/gitconfig

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
git-spicecliglobales 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.31.2
Manager aktualisiert2026-07-21
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.31.2

https://github.com/abhinav/git-spice

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:git-spice
Version0.31.2
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/git-spice
Homepagehttps://abhinav.github.io/git-spice/
Repositoryhttps://github.com/abhinav/git-spice
Upstream-Dokumentationhttps://abhinav.github.io/git-spice
LizenzGPL-3.0-or-later
Quellarchivhttps://github.com/abhinav/git-spice/archive/refs/tags/v0.31.2.tar.gz
Zuletzt aktualisiert2026-07-21T16:54:58Z
Pulseupdated
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert
EinschränkungenThe 'gs' executable has been renamed to 'git-spice'. If you prefer to use 'gs', add an alias to your shell configuration: alias gs='git-spice'

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namegit-spice
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%

git-spice

nix profile install nixpkgs#git-spice
  • normalized package name match
  • Abgeglichen nach: Git Spice
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/gi/git-spice/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 configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment