macOS
Homebrewverified · 100%
brew install gitslavelocal Homebrew formula metadata
brew / rank 11935
Install gitslave with Homebrew, zypper
Create group of related repos with one as superproject. Version 2.0.2 via Homebrew; verified from local package data. Also installable with zypper: sudo zypper install gitslave.
install
Additional install commands
Linux
openSUSE zypperverified · 92%
sudo zypper install gitslaveopenSUSE Tumbleweed package metadata · gitslave · source: download.opensuse.org
overview
Package summary
Create group of related repos with one as superproject
Project links
Commands and aliases
- gits
history
Project history and usage
Gitslave is a Git-era multi-repository management tool built around a `gits` wrapper command. It organizes a superproject and related slave repositories so common Git operations can be applied across the group.
Project history
The official site and man page describe Gitslave as a response to the limitations of Git submodules for projects that need active development across several repositories. Release notes show a 2.0 release in March 2011 and a 2.0.2 release in January 2012, with features such as recursive subprojects, tutorial documentation, reference clone support, and limited Windows support.
Adoption history
Gitslave's own documentation says it was used for mid-sized product development with many slave repositories, branches, tags, and developers, as well as for smaller personal setups that kept related editor configuration repositories in sync. Its niche was teams that wanted a CVS- or SVN-like multi-directory workflow while retaining separate Git repositories.
How it is used
Practitioners create or clone a superproject, run setup commands such as `gits prepare`, attach related repositories, and then use `gits` for operations such as clone, populate, branch, commit, push, pull, merge, tag, checkout, status, and log. The `.gitslave` file records repository relationships for the superproject.
Why package nerds care
For package history, Gitslave is a useful artifact from the period when Git users were experimenting with alternatives to submodules, repo-style workflows, monorepos, and multi-SCM tools such as mr. It shows how package ecosystems captured local workflow tools that were important to a specific development style even without becoming mainstream Git features.
Timeline
- 2011: Gitslave 2.0 released with recursive subprojects and tutorial documentation.
- 2011: Gitslave 2.0.1 added broader Git resource locator handling and pager support.
- 2012: Gitslave 2.0.2 added reference-clone support and documented limited Windows use.
Related projects
- Gitslave is related to Git submodules, Google's repo tool, monorepo and subtree workflows, and mr for managing multiple repositories.
Sources
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 bottle metadata was recorded.
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
.gitslave
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
gits | executable | indexed executable | Discovered from the local executable index. |
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-08-03
manager version2.0.2
manager updated
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:gitslave |
|---|---|
| Version | 2.0.2 |
| Package manager | Homebrew |
| Homepage | https://gitslave.sourceforge.net/ |
| Bottle | not recorded |
| Service | none declared |
source database matches
Other package-manager records
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
zypper95%
gitslave 2.0.2-10.7
Creates a group of related repositories
http://gitslave.sourceforge.net
sudo zypper install gitslave- License: SUSE-Gitslave
- Category: Development/Tools/Version Control
- Architecture: noarch
- Source Package: gitslave
- 3 dependencies
- 1 provides
- normalized package name match
- Matched by: Gitslave
zypper95%
gitslave-doc 2.0.2-10.7
Documentation for gitslave
http://gitslave.sourceforge.net
sudo zypper install gitslave-doc- License: SUSE-Gitslave
- Category: Development/Tools/Version Control
- Architecture: noarch
- Source Package: gitslave
- 1 provides
- normalized package name match
- Matched by: Gitslave
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.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- external package-manager database matches
- pkg.so package database
- pkgdb category and tag curation