Automic VaultAutomic Vault

brew

Install git-flow with Homebrew, apk, apt, MacPorts, winget

Extensions to follow Vincent Driessen's branching model. Version 0.4.1 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install git-flow

local Homebrew formula metadata

MacPortsverified · 94%
sudo port install git-flow

MacPorts ports tree · devel/git-flow/Portfile · source: api.github.com

Linux

Alpine Linux apkverified · 92%
sudo apk add git-flow

Alpine Linux edge package indexes · git-flow · source: dl-cdn.alpinelinux.org

Debian aptverified · 92%
sudo apt install git-flow

Debian stable package indexes · git-flow · source: deb.debian.org

Windows

Windows Package Managerverified · 92%
winget install --id GitTower.GitFlowNext -e

Windows Package Manager source index · GitTower.GitFlowNext · source: cdn.winget.microsoft.com

overview

Package summary

Extensions to follow Vincent Driessen's branching model

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.

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 1 platform targets.

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

CommandKindExposureNote
git-flowcliglobal 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.4.1
manager updated
local dataok
upstreamcurrent
latest detected0.4.1

https://github.com/nvie/gitflow

  • infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package keybrew:git-flow
Version0.4.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/git-flow
Homepagehttps://github.com/nvie/gitflow
Repositoryhttps://github.com/nvie/gitflow
Upstream docshttps://github.com/nvie/gitflow#readme
LicenseBSD-2-Clause
Source archivehttps://github.com/nvie/gitflow/archive/refs/tags/0.4.1.tar.gz
Bottleavailable (on all)
Homebrew post-installnot defined
Servicenone declared
CaveatsTo install Zsh completions: brew install zsh-completions

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namegit-flow
Version Scheme0
Revision1
Head VersionHEAD
Conflicts With
  • git-flow-next
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedyes
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.

Debian apt95%

git-flow 1.12.3-3

Git extension to provide a high-level branching model

https://github.com/petervanderdoes/gitflow/wiki

sudo apt install git-flow
  • Section: vcs
  • Architecture: all
  • 2 dependencies
  • normalized package name match
  • Matched by: Git Flow
Debian stable package indexes · deb.debian.org · Debian stable package indexes: git-flow from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz
Ubuntu apt95%

git-flow 1.12.3-3

Git extension to provide a high-level branching model

https://github.com/petervanderdoes/gitflow/wiki

sudo apt install git-flow
  • Section: universe/vcs
  • Architecture: all
  • 2 dependencies
  • normalized package name match
  • Matched by: Git Flow
Ubuntu 24.04 LTS package indexes · archive.ubuntu.com · Ubuntu 24.04 LTS package indexes: git-flow from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz
apk95%

git-flow 1.12.3-r1

Git extension to provide a high-level branching model

https://github.com/petervanderdoes/gitflow-avh

sudo apk add git-flow
  • License: LGPL-2.1-or-later
  • Architecture: x86_64
  • Source Package: git-flow
  • 1 dependencies
  • 1 provides
  • normalized package name match
  • Matched by: Git Flow
Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: git-flow from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
apk95%

git-flow-doc 1.12.3-r1

Git extension to provide a high-level branching model (documentation)

https://github.com/petervanderdoes/gitflow-avh

sudo apk add git-flow-doc
  • License: LGPL-2.1-or-later
  • Architecture: x86_64
  • Source Package: git-flow
  • normalized package name match
  • Matched by: Git Flow
Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: git-flow-doc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
MacPorts95%

git-flow

sudo port install git-flow
  • normalized package name match
  • Matched by: Git Flow
MacPorts ports tree · api.github.com · MacPorts ports tree: devel/git-flow/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
winget95%

GitTower.GitFlowNext

winget install --id GitTower.GitFlowNext -e
  • normalized package name match
  • Matched by: Git Flow
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: GitTower.GitFlowNext from https://cdn.winget.microsoft.com/cache/source.msix

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 package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment