brew / Approval Gates

git mit Homebrew, apk, chocolatey, apt, dnf, MacPorts, Nix, pacman, zypper, scoop, winget installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für git in AI-Agent-Workflows.

Installationsbefehl Sicherheitshinweise

Agent-Sicherheit

Antwort zur Agent-Sicherheit

git can read repository history and mutate source-control state used by agents and humans.

Credential-Zugriff

Reads credential helpers, remotes, config, signed keys, and repository-local secret history.

Änderungen an Remote-Zustand

Can push commits, tags, branches, and force updates to remote repositories.

Publish-/Artefakt-Risiko

Can publish source changes and release tags that downstream systems consume.

Empfohlene Kontrolle

Gate pushes, tag creation, credential fill, and remote rewrites.

Hinweise für Agent-Nutzung

Allow diff/status/log reads; require approval for pushes, credential-helper reads, and destructive history changes.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install git

local Homebrew formula metadata

MacPortsverifiziert · 94%

sudo port install git

MacPorts ports tree · devel/git/Portfile · Quelle: api.github.com

Linux

Alpine Linux apkverifiziert · 92%

sudo apk add git

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

Debian aptverifiziert · 92%

sudo apt install git

Debian stable package indexes · git · Quelle: deb.debian.org

Fedora dnfverifiziert · 92%

sudo dnf install git

Fedora Rawhide package metadata · git · Quelle: dl.fedoraproject.org

Nixverifiziert · 92%

nix profile install nixpkgs#git

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

Arch Linux pacmanverifiziert · 92%

sudo pacman -S git

Arch Linux sync databases · git · Quelle: geo.mirror.pkgbuild.com

openSUSE zypperverifiziert · 92%

sudo zypper install git

openSUSE Tumbleweed package metadata · git · Quelle: download.opensuse.org

Windows

Chocolateyverifiziert · 92%

choco install git

Chocolatey community package catalog · git · Quelle: community.chocolatey.org

Scoopverifiziert · 92%

scoop install main/git

Scoop official bucket manifest trees · bucket/git.json · Quelle: api.github.com

Windows Package Managerverifiziert · 92%

winget install --id DuckStudio.ChineseGit -e

Windows Package Manager source index · DuckStudio.ChineseGit · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

Distributed revision control system

Projektlinks

Befehle und Aliase

git
git-cvsserver
git-receive-pack
git-shell
git-upload-archive
git-upload-pack
scalar

Verlauf

Projektgeschichte und Nutzung

Git is the distributed version-control system created for Linux kernel development and later generalized into the default source-control substrate for much of software development. Its command-line interface, repository format, protocol family, and ecosystem of hosting services define how many projects exchange code.

Projektgeschichte

Git began in 2005 after the Linux kernel community lost access to the proprietary BitKeeper workflow it had been using. Linus Torvalds wrote the original implementation to support Linux-scale development, emphasizing speed, integrity, distributed operation, and cheap branching.

The design departed from centralized version-control systems by making every clone a full repository with local history and branch operations. That choice made offline work, fork-based development, and patch exchange natural rather than exceptional.

After its Linux origin, Git evolved into a broadly portable tool with a large manual set, porcelain commands for everyday work, and plumbing commands for scripts and higher-level tools. The kernel.org repository remains the canonical upstream source location, while git-scm.com provides the public documentation hub.

Adoptionsgeschichte

Git's adoption accelerated with distributed open source development and the rise of Git hosting services such as GitHub, GitLab, and related forges. The official Git site characterizes the core project as a command-line tool surrounded by hosting services, graphical clients, editor integrations, and other command-line helpers.

By the early 2010s, Git had moved from a Linux-kernel tool into the common denominator for open source collaboration, commercial software teams, CI systems, package ecosystems, and code review platforms. Its repository model also became the foundation for workflows outside source code, including documentation and data-adjacent projects.

Wie es verwendet wird

Practitioners use Git to initialize or clone repositories, stage and commit changes, branch and merge work, inspect history, exchange commits through remotes, and recover earlier states. Its local-first model makes common commands fast because most history and metadata are on the developer's machine.

Teams layer policy on top of Git through protected branches, pull requests, signed commits, release tags, submodules, worktrees, hooks, and CI triggers. The same executable serves both interactive daily work and automation in release scripts, package recipes, deployment systems, and source archives.

Warum Paket-Nerds sich dafür interessieren

Git is one of the central dependencies of package-manager culture. Formulae, ports, distro source packages, language registries, and build systems routinely fetch from Git repositories, pin commits or tags, generate source archives, and use Git metadata to derive versions.

Its significance also comes from its stability as an interchange format. Even tools that wrap Git, avoid the Git CLI, or store files elsewhere usually need to speak in Git concepts: commits, refs, remotes, branches, tags, diffs, and patches.

Zeitleiste

2005: Git was created for Linux kernel development after the BitKeeper transition.
2005: Early Git releases established the distributed repository model.
2010s: Hosted Git forges and pull-request workflows made Git the dominant version-control system for many developer communities.
2020s: Git remained a base dependency for package managers, CI, source archives, and developer tools.

Related projects

Linux kernel development drove Git's original requirements.
GitHub, GitLab, Gitea, Forgejo, and other forges build hosted collaboration around Git repositories.
Git LFS and Git Xet extend Git workflows for large-file storage.
Scalar, included with Git packages, targets very large repository workflows.

Quellen

Approval Gates

Metadaten für menschliche Prüfung riskanter Befehle

Der lokale Approval-Gate-Seed enthält 6 Regeln für git. Abgedeckte Einstiegspunkte: git. Schweregrade: kritisch, hoch, mittel. Abdeckung: partial, geprüft am 2026-05-21.

Beispiele für gated Aktionen

Push commits, tags, or refs to a remote repository.
Force-push or delete remote refs.
Reset local worktree and index destructively.
Delete untracked files from the worktree.
Read, approve, reject, or fill credentials through Git credential helpers.
Change credential helper configuration.

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.

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix: ~/.git-credentials

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit
`git`	cli	globales Executable
`git-cvsserver`	cli	globales Executable
`git-receive-pack`	cli	globales Executable
`git-shell`	cli	globales Executable
`git-upload-archive`	cli	globales Executable
`git-upload-pack`	cli	globales Executable
`scalar`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-10

Manager-Version2.55.0

Manager aktualisiert2026-06-29

lokale DatenOK

Upstreamnot checked

neueste erkannte Versionnicht erkannt

https://git-scm.com

InfoRelease/tag comparison is only available for GitHub repositories.https://git-scm.comnone Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:git
Version	2.55.0
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/git
Homepage	https://git-scm.com
Repository	https://git.kernel.org/pub/scm/git/git.git
Upstream-Dokumentation	https://git-scm.com/doc
Lizenz	GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.1-or-later AND BSD-3-Clause AND MIT
Quellarchiv	https://mirrors.edge.kernel.org/pub/software/scm/git/git-2.55.0.tar.xz
Zuletzt aktualisiert	2026-06-29T20:54:53Z
Pulse	updated
Abhängigkeiten	gettext, pcre2
Build-Abhängigkeiten	gettext, pkgconf
Von macOS bereitgestellte Bibliotheken	curl, expat
Bottle	verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert
Einschränkungen	The Tcl/Tk GUIs (e.g. gitk, git-gui) are now in the `git-gui` formula. Subversion interoperability (git-svn) is now in the `git-svn` formula.

Registry-Fakten

Details aus der Quelldatenbank

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	git
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Debian apt95%

git 1:2.47.3-0+deb13u1

fast, scalable, distributed revision control system