# git-vendor を Homebrew, Nix でインストール

git-vendor のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

```sh
sudo av install brew:git-vendor
```

追加のインストールコマンド:

### macOS

- Homebrew (100%):

```sh
brew install git-vendor
```

  証拠: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#git-vendor
```

  証拠: nixpkgs package indexes: pkgs/by-name/gi/git-vendor/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## パッケージ情報

- **パッケージキー:** brew:git-vendor
- **パッケージマネージャ:** Homebrew
- **バージョン:** 1.3.0
- **ソース概要:** Command for managing git vendored dependencies
- **ホームページ:** <https://brettlangdon.github.io/git-vendor>
- **リポジトリ:** <https://github.com/brettlangdon/git-vendor>
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- git-vendor (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 1.3.0
## プロジェクトの歴史と使われ方

git-vendor is a shell Git command that wraps git subtree to add, list, update, and share vendored dependencies.

### プロジェクトの歴史

Brett Langdon created the git-vendor repository in January 2016. The README explains that the tool follows the Go vendoring convention of storing dependencies under vendor/ using fully qualified project paths.

The project stayed close to git subtree. Later releases refined command behavior, including a 2022 release that added a push command through a community contribution.

### 採用の歴史

git-vendor spread through source installation, Homebrew, and other package-manager formulas. Its adoption niche was teams that wanted vendored source checked into a repository without relying on language-specific package managers.

### 使われ方

Practitioners use git vendor add to import a repository at a ref, git vendor list to inspect recorded source metadata, git vendor update to move a vendored dependency forward, and git vendor upstream to share changes back.

### パッケージ好きにとっての重要性

The tool is significant in package-management history because it captures a pre-module and cross-language vendoring pattern: source is copied into the tree, but the Git history and vendor metadata preserve where that source came from.

### タイムライン

- 2016: Repository created for a git subtree-based vendoring workflow.
- 2021: v1.2.x releases refined update behavior and portability.
- 2022: v1.3.0 added a push command.

### Related projects

- git subtree, Go vendor directories, Homebrew

### ソース

- <https://brettlangdon.github.io/git-vendor>
- <https://formulae.brew.sh/formula/git-vendor>
- <https://github.com/brettlangdon/git-vendor>
- <https://github.com/brettlangdon/git-vendor/releases>
- <https://raw.githubusercontent.com/brettlangdon/git-vendor/master/README.md>


## セキュリティノート

narrow executable package without higher-risk signals.

- **Geiger リスク:** グリーン / 低
- narrow executable package without higher-risk signals

## 他のパッケージマネージャ記録

- Nix - git-vendor: normalized package name match | nixpkgs package indexes: pkgs/by-name/gi/git-vendor/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/git-vendor.yml](https://github.com/mxcl/pkgdb/blob/main/combined/git-vendor.yml)


## ソース

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph