Automic VaultAutomic Vault

brew

Install git-spice with Homebrew, Nix

Manage stacked Git branches. Version 0.30.1 via Homebrew; verified 2026-07-02.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install git-spice

local Homebrew formula metadata

Linux

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

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

overview

Package summary

Manage stacked Git branches

Commands and aliases

  • git-spice

history

Project history and usage

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

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

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

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

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

Installed executables

CommandKindExposureNote
git-spicecliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version0.30.1
manager updated2026-07-02
local dataok
upstreamcurrent
latest detectedv0.30.1

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

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:git-spice
Version0.30.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/git-spice
Homepagehttps://abhinav.github.io/git-spice/
Repositoryhttps://github.com/abhinav/git-spice
Upstream docshttps://abhinav.github.io/git-spice
LicenseGPL-3.0-or-later
Source archivehttps://github.com/abhinav/git-spice/archive/refs/tags/v0.30.1.tar.gz
Last updated2026-07-02T16:40:56Z
Pulseupdated
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared
CaveatsThe '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 facts

Source database details

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 database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

git-spice

nix profile install nixpkgs#git-spice
  • normalized package name match
  • Matched by: 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

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • 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