# ghr を Homebrew, Nix, winget でインストール

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

## インストール

```sh
sudo av install brew:ghr
```

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

### macOS

- Homebrew (100%):

```sh
brew install ghr
```

  証拠: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#ghr
```

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

### Windows

- winget (92%):

```sh
winget install --id cataggar.ghr -e
```

  証拠: Windows Package Manager source index: cataggar.ghr from https://cdn.winget.microsoft.com/cache/source.msix

## パッケージ情報

- **パッケージキー:** brew:ghr
- **パッケージマネージャ:** Homebrew
- **バージョン:** 0.18.3
- **ソース概要:** Upload multiple artifacts to GitHub Release in parallel
- **ホームページ:** <https://github.com/tcnksm/ghr>
- **リポジトリ:** <https://github.com/tcnksm/ghr>
- **最終更新:** 2026-07-25T20:55:22-04:00
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- ghr (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

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

ghr is a release-engineering CLI for creating GitHub Releases and uploading release artifacts in parallel.

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

The ghr repository was created in July 2014, with an initial v0.1.0 release published days later. Its README presents a Go-oriented release workflow: build artifacts, tag a release, and use `ghr TAG PATH` to create a GitHub Release and upload the files.

The tool developed around the practical needs of release automation: reading repository information from `.git/config`, accepting `GITHUB_TOKEN`, supporting GitHub Enterprise through `GITHUB_API`, replacing or recreating assets, marking draft or prerelease releases, and later exposing a GitHub Action wrapper for workflow files.

### 採用の歴史

ghr became useful in the era when projects began publishing multi-platform binaries as GitHub Release assets. The README's demo centers on cross-compiled Go binaries, and the documented Action support shows how the same tool moved into CI-based release pipelines.

### 使われ方

Practitioners use ghr after a build job has produced a directory of archives, checksums, installers, or other assets. A typical run supplies a tag and path, with optional title, body, commitish, draft, prerelease, replace, delete, generated notes, and parallel upload settings.

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

Package nerds care about ghr because it is release plumbing: it turns build output into a GitHub Release page with assets, which downstream package managers and install scripts often consume.

### タイムライン

- 2014: GitHub repository created.
- 2014: v0.1.0 initial release published.
- 2021: GitHub automatic release notes support arrived in GitHub, and ghr later documented a `-generatenotes` flag.
- 2020s: README documents a reusable GitHub Action interface.

### Related projects

- The README compares ghr with aktau/github-release and connects it to GitHub Releases, GitHub Enterprise, GitHub Actions, Go cross-compilation, checksums, and CI build artifacts.

### ソース

- <https://api.github.com/repos/tcnksm/ghr>
- <https://github.com/tcnksm/ghr>
- <https://github.com/tcnksm/ghr#readme>
- <https://github.com/tcnksm/ghr/releases/tag/v0.1.0>
- <https://pkg.go.dev/github.com/tcnksm/ghr>


## セキュリティノート

broad file, network, media, or database tool signal.

- **Geiger リスク:** blue / 中
- broad file, network, media, or database tool signal

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

- Nix - ghr: normalized package name match | nixpkgs package indexes: pkgs/by-name/gh/ghr/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- winget - cataggar.ghr: normalized package name match | Windows Package Manager source index: cataggar.ghr from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

View the package source record on GitHub. [combined/ghr.yml](https://github.com/mxcl/pkgdb/blob/main/combined/ghr.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