Automic VaultAutomic Vault

brew

github-release mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install github-release

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#github-release

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

Überblick

Paketzusammenfassung

Create and edit releases on Github (and upload artifacts)

Befehle und Aliase

  • github-release

Verlauf

Projektgeschichte und Nutzung

github-release is a Go command-line utility for creating, editing, deleting, inspecting, and uploading files to GitHub Releases. It belongs to the early generation of single-purpose release automation tools that wrapped GitHub's Releases API before GitHub's own CLI became the default tool for many workflows.

Projektgeschichte

The project repository was created in January 2014, soon after GitHub exposed Releases as an API-backed feature. Its README framed the tool as a friendlier alternative to doing release and artifact work with raw HTTP requests, especially because uploads require resolving release identifiers before attaching files.

The project retained a narrow scope: tags and releases stay in GitHub, while the CLI handles the API calls needed to create release records, edit metadata, upload artifacts, and delete releases. Copyright notices in the README identify Nicolas Hillegeer for the original 2014-2017 period and Meter, Inc. for later maintenance.

Adoptionsgeschichte

github-release became useful in build scripts that produced binaries before GitHub Actions and the GitHub CLI were widely adopted. Its packaging in Homebrew and Nix reflects the role it played for developers who wanted a small standalone executable rather than a larger platform CLI.

The tool's continued packaging gives older CI and release scripts a stable command name. That matters for projects that still publish GitHub Release assets from Makefiles, shell scripts, or external CI systems.

Wie es verwendet wird

Practitioners use github-release by exporting a GitHub token, tagging and pushing a repository, then running subcommands such as `release`, `edit`, `upload`, `delete`, and `info`. The README also documents `GITHUB_API`, which lets the same workflow target a GitHub Enterprise API endpoint.

Warum Paket-Nerds sich dafür interessieren

For package maintainers, github-release is notable because it automates the exact step that many package recipes depend on: publishing versioned binary artifacts on GitHub Releases. It is a compact example of a tool whose job is not building software, but making the release surface predictable enough for downstream package managers.

Zeitleiste

  • 2014: Repository created for a Go CLI around GitHub Releases.
  • 2014: README examples show release creation, editing, artifact upload, deletion, and release inspection.
  • 2020: Maintenance copyright notice added for Meter, Inc.
  • 2025: v0.11.0 release published on GitHub.

Related projects

  • Related tools include GitHub's Releases API, GitHub Enterprise, GitHub CLI, and CI systems that publish build artifacts to GitHub Releases.

Sicherheitslage

Risikostufe: blue

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

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

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

Signale

  • text:upload

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 8 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
github-releasecliglobales 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-25
Manager-Version0.11.0
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.11.0

https://github.com/github-release/github-release

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:github-release
Version0.11.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/github-release
Homepagehttps://github.com/github-release/github-release
Repositoryhttps://github.com/github-release/github-release
Upstream-Dokumentationhttps://github.com/github-release/github-release#readme
LizenzMIT
Quellarchivhttps://github.com/github-release/github-release/archive/refs/tags/v0.11.0.tar.gz
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namegithub-release
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
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.

Nix95%

github-release

nix profile install nixpkgs#github-release
  • normalized package name match
  • Abgeglichen nach: Github Release
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/gi/github-release/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment