pkg.soopen package index

brew / rank 1083

Install ghr with Homebrew, Nix, winget

Upload multiple artifacts to GitHub Release in parallel. Version 0.18.3 via Homebrew; verified 2026-07-25. Also installable with nix: nix profile install nixpkgs#ghr.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install ghr

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#ghr

nixpkgs package indexes · pkgs/by-name/gh/ghr/package.nix · source: api.github.com

Windows

Windows Package Managerverified · 92%
winget install --id cataggar.ghr -e

Windows Package Manager source index · cataggar.ghr · source: cdn.winget.microsoft.com

overview

Package summary

Upload multiple artifacts to GitHub Release in parallel

Commands and aliases

  • ghr

history

Project history and usage

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

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

  • 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.

security posture

Risk level: blue

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

Risk classifier

blue risk · medium confidence · tool

Why

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

Signals

  • text:upload

Install behavior

  • No Homebrew bottle metadata was recorded.

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
ghrexecutableindexed executableDiscovered from the local executable index.

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-08-03
manager version0.18.3
manager updated2026-07-25
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:ghr
Version0.18.3
Package managerHomebrew
Homepagehttps://github.com/tcnksm/ghr
Repositoryhttps://github.com/tcnksm/ghr
Last updated2026-07-25T20:55:22-04:00
Pulseupdated
Bottlenot recorded
Servicenone declared

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

ghr

nix profile install nixpkgs#ghr
  • normalized package name match
  • Matched by: Ghr
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/gh/ghr/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
winget95%

cataggar.ghr

winget install --id cataggar.ghr -e
  • normalized package name match
  • Matched by: Ghr
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: cataggar.ghr 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
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • pkg.so package database
  • pkgdb category and tag curation