sécurité des agents

Réponse sur la sécurité des agents

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

Accès aux identifiants

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

Modification distante

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

Risque de publication ou d'artéfact

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

Contrôle recommandé

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

Conseils d'utilisation par les agents

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

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%

brew install git

local Homebrew formula metadata

MacPortsvérifié · 94%

sudo port install git

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

Linux

Alpine Linux apkvérifié · 92%

sudo apk add git

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

Debian aptvérifié · 92%

sudo apt install git

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

Fedora dnfvérifié · 92%

sudo dnf install git

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

Nixvérifié · 92%

nix profile install nixpkgs#git

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

Arch Linux pacmanvérifié · 92%

sudo pacman -S git

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

openSUSE zyppervérifié · 92%

sudo zypper install git

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

Windows

Chocolateyvérifié · 92%

choco install git

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

Scoopvérifié · 92%

scoop install main/git

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

Windows Package Managervérifié · 92%

winget install --id DuckStudio.ChineseGit -e

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

aperçu

Résumé du paquet

Distributed revision control system

Liens du projet

Commandes et alias

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

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

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.

Sources

portes d'approbation

Métadonnées de revue humaine pour commandes risquées

La graine locale de portes d'approbation contient 6 règles pour git. Points d'entrée couverts : git. Niveaux de sévérité : critique, élevé, moyen. Couverture : partial, revu le 2026-05-21.

Exemples d'actions contrôlées

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

exécutables

Exécutables installés

Commande	Type	Exposition
`git`	cli	exécutable global
`git-cvsserver`	cli	exécutable global
`git-receive-pack`	cli	exécutable global
`git-shell`	cli	exécutable global
`git-upload-archive`	cli	exécutable global
`git-upload-pack`	cli	exécutable global
`scalar`	cli	exécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-10

version du gestionnaire2.55.0

gestionnaire mis à jour2026-06-29

données localesOK

amontnot checked

dernière version détectéenon détecté

https://git-scm.com

infoRelease/tag comparison is only available for GitHub repositories.https://git-scm.comconfiance none

métadonnées d'installation

Métadonnées du paquet

Clé du paquet	brew:git
Version	2.55.0
Gestionnaire de paquets	Homebrew
Page du gestionnaire de paquets	https://formulae.brew.sh/formula/git
Page d'accueil	https://git-scm.com
Dépôt	https://git.kernel.org/pub/scm/git/git.git
Docs amont	https://git-scm.com/doc
Licence	GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.1-or-later AND BSD-3-Clause AND MIT
Archive source	https://mirrors.edge.kernel.org/pub/software/scm/git/git-2.55.0.tar.xz
Dernière mise à jour	2026-06-29T20:54:53Z
Pulse	updated
Dépendances	gettext, pcre2
Dépendances de compilation	gettext, pkgconf
Bibliothèques fournies par macOS	curl, expat
Bouteille	disponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrew	non défini
Service	aucun déclaré
Précautions	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.

faits du registre

Détails de la base source

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

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Debian apt95%

git 1:2.47.3-0+deb13u1

fast, scalable, distributed revision control system

Installer git avec Homebrew, apk, chocolatey, apt, dnf, MacPorts, Nix, pacman, zypper, scoop, winget