pkg.sopackage field notes

brew / portes d'approbation / rang 7

Installer gh avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de gh pour les workflows d'agents IA.

sécurité des agents

Réponse sur la sécurité des agents

gh is the GitHub control-plane CLI for repositories, releases, issues, and authenticated developer state.

Accès aux identifiants

Reads GitHub CLI tokens and can print or use them for API calls.

Modification distante

Can modify repositories, pull requests, releases, secrets, and organization state.

Risque de publication ou d'artéfact

Can create releases, upload assets, and trigger release automation.

Contrôle recommandé

Use GitHub token protection plus approval gates for write and token-display commands.

Conseils d'utilisation par les agents

Permit status and read-only queries; require approval for token output, release creation, repo writes, and workflow dispatch.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install gh

provider-native install command

aperçu

Résumé du paquet

GitHub command-line tool

Commandes et alias

  • gh

historique

Historique du projet et usages

GitHub CLI, invoked as `gh`, is GitHub's official command-line tool for working with pull requests, issues, repositories, releases, Actions, authentication, and GitHub API data from a terminal.

Historique du projet

GitHub created the cli/cli repository in October 2019 and opened the project as a new official CLI distinct from the older community `hub` tool. GitHub announced the beta in February 2020 and released GitHub CLI 1.0 in September 2020.

The README frames `gh` as a standalone tool that brings GitHub concepts next to `git` and source code work. The project grew into a cross-platform Go CLI with first-party manuals, release binaries, package repositories, GitHub Enterprise support, extension support, API helpers, and later supply-chain features such as build provenance attestations for release artifacts.

Historique d'adoption

GitHub CLI has broad adoption because it is distributed through GitHub's own package repositories and release binaries, package managers such as Homebrew and WinGet, and GitHub-hosted Actions runner images. Its first-party status made it a standard automation interface for GitHub workflows in shells and CI jobs.

Modes d'utilisation

Practitioners use `gh` to create and review pull requests, triage issues, clone and browse repositories, trigger or inspect Actions workflows, manage releases and gists, authenticate to GitHub hosts, call the GitHub API, and script repository operations without leaving the command line.

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

For package and automation ecosystems, `gh` is important because it gives GitHub an official, versioned executable surface. Package maintainers can depend on consistent commands across macOS, Linux, and Windows, while CI authors can use a preinstalled or easily installed binary instead of hand-rolling API calls.

Chronologie

  • 2019: The cli/cli repository was created.
  • 2020: GitHub announced GitHub CLI beta.
  • 2020: GitHub CLI 1.0.0 was published.
  • 2024: The README records release build provenance attestations beginning with version 2.50.0.

Related projects

  • The README compares GitHub CLI with `hub`, noting that `hub` behaves as a proxy to `git` while `gh` is a standalone tool for GitHub workflows.

portes d'approbation

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

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

Exemples d'actions contrôlées

  • Print the active GitHub authentication token.
  • Create or refresh local GitHub authentication state.
  • Delete a GitHub repository.
  • Change repository settings, visibility, topics, or metadata.
  • Merge a pull request.
  • Create, upload to, edit, or delete GitHub releases.
  • Trigger a GitHub Actions workflow.

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.

Configuration files

Config paths the tool may read or write during local use.

Unix
$XDG_CONFIG_HOME/gh/config.yml~/.config/gh/config.yml
Windows
%AppData%\GitHub CLI\config.yml

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
$XDG_CONFIG_HOME/gh/hosts.yml~/.config/gh/hosts.yml
Windows
%AppData%\GitHub CLI\hosts.yml

exécutables

Exécutables installés

CommandeTypeExpositionNote
ghexécutableexécutable indexéDécouvert depuis l'index local des exécutables.

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-08-03
version du gestionnaire2.97.0
gestionnaire mis à jour2026-07-31
données localesinconnu
amontnon disponible
dernière version détectéenon détecté
  • OKAucun avertissement de fraîcheur n'a été généré.

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:gh
Version2.97.0
Gestionnaire de paquetsHomebrew
Page d'accueilhttps://cli.github.com/
Dépôthttps://github.com/cli/cli
Dernière mise à jour2026-07-31T05:32:54Z
Pulseupdated
Bouteillenon enregistré
Serviceaucun déclaré

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/gh.yml

Sources utilisées

  • Geiger risk classifier
  • Nucleus package database
  • approval-gate seed metadata
  • curated agent safety answer
  • curated configuration and credential file locations
  • curated package history
  • pkgdb category and tag curation