macOS
Homebrewverified · 100%
brew install git-trackerlocal Homebrew formula metadata
brew / rank 15850
Install git-tracker with Homebrew
Integrate Pivotal Tracker into your Git workflow. Version 2.0.0 via Homebrew; verified 2026-06-22.
install
Additional install commands
overview
Package summary
Integrate Pivotal Tracker into your Git workflow
Project links
Commands and aliases
- git-tracker
history
Project history and usage
git-tracker is a Git hook helper for teams that name branches with Pivotal Tracker story numbers. It installs a prepare-commit-msg hook that detects a story ID in the branch name and adds the corresponding Tracker syntax to commit messages.
Project history
The upstream git_tracker repository was created in 2012 by Steven Harman. Its README presents the tool as GitTracker or git-tracker, a small workflow bridge between local Git branches and Pivotal Tracker's commit-message conventions.
Adoption history
Adoption appears concentrated around Ruby and macOS/Homebrew users rather than a broad Git ecosystem. The project is published as the git_tracker RubyGem and as the git-tracker Homebrew formula, both pointing back to the same GitHub source repository.
How it is used
Practitioners install the binary, run `git tracker init` inside each repository where the hook should be active, and include a Pivotal Tracker story number in branch names. On commit, the hook adds a Tracker-formatted story marker, or a keyword such as Fixes with the story number, unless the message already contains the marker.
Why package nerds care
The package is a compact example of Git's extension culture: a Ruby-distributed tool exposed as a `git tracker` subcommand, with most behavior implemented by installing a standard Git hook into each repository.
Timeline
- 2012: git_tracker repository created.
- 2.0.0: RubyGems and Homebrew package the tool under git_tracker and git-tracker names.
Related projects
- git-tracker is tied to Git hooks, Pivotal Tracker's source-control message syntax, RubyGems packaging, and Homebrew distribution.
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.
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
git-tracker | 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.0
manager updated2026-06-22
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:git-tracker |
|---|---|
| Version | 2.0.0 |
| Package manager | Homebrew |
| Homepage | https://github.com/stevenharman/git_tracker |
| Repository | https://github.com/stevenharman/git_tracker |
| Last updated | 2026-06-22T14:03:32-07:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
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 package history
- pkg.so package database
- pkgdb category and tag curation