macOS
Homebrewverified · 100%
brew install git-flowprovider-native install command
brew / rank 1004
Install git-flow with Homebrew
Extensions to follow Vincent Driessen's branching model. Version 0.4.1 via Homebrew; verified from local package data.
install
Additional install commands
overview
Package summary
Extensions to follow Vincent Driessen's branching model
Project links
Commands and aliases
- git-flow
history
Project history and usage
git-flow is the original command-line extension package for Vincent Driessen's Git branching model, providing high-level commands for feature, release, hotfix, and support branches.
Project history
Driessen published the branching model on January 5, 2010 and opened the gitflow repository later that month. The model organized release-oriented development around long-lived master and develop branches plus short-lived feature, release, and hotfix branches. The command package encoded that procedure as `git flow init`, `git flow feature`, `git flow release`, `git flow hotfix`, and related subcommands.
Adoption history
The model became one of the most recognizable Git workflow patterns of the 2010s. Driessen's 2020 reflection says many software teams treated git-flow almost like a standard, while also cautioning that continuously delivered web applications often benefit from simpler workflows such as GitHub Flow. The original repository's README later thanked users for more than fifteen years of adoption and pointed to git-flow-next as the maintained successor.
How it is used
Practitioners used git-flow to initialize branch naming conventions, start feature branches from develop, finish them back into develop, prepare release branches, and apply urgent fixes from master through hotfix branches. The CLI wrapped ordinary Git branch, merge, tag, publish, and pull operations into named release-management steps.
Why package nerds care
git-flow is significant in package-manager culture because it turned a blog-post workflow into an installable Git extension. Its formulae and distro packages made `git flow` a standard command on developer machines, even as later teams debated whether the workflow fit CI/CD-heavy projects.
Timeline
- 2010: Driessen published the successful Git branching model.
- 2010: The gitflow repository began and early 0.x releases followed.
- 2020: Driessen added a reflection warning against dogmatic use for continuous-delivery web applications.
- 2025: The original repository marked git-flow-next as the maintained successor.
Related projects
- git-flow influenced git-flow-avh, git-flow-completion, Tower's Git-flow integration, and git-flow-next.
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-flow | 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 version0.4.1
manager updated
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:git-flow |
|---|---|
| Version | 0.4.1 |
| Package manager | Homebrew |
| Homepage | https://github.com/nvie/gitflow |
| Repository | https://github.com/nvie/gitflow |
| 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
- Nucleus package database
- curated package history
- pkgdb category and tag curation