Skip to content
Back to search

cli

GitHub’s official command line tool

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/cli/cli with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/cli/cli'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/cli-cli/badge.svg)](/listings/cli-cli)

HTML

<a href="/listings/cli-cli"><img src="/api/listings/cli-cli/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

[macOS](docs/install_macos.md)

- [Homebrew](docs/install_macos.md#homebrew) - [Precompiled binaries](docs/install_macos.md#precompiled-binaries) on [releases page][]

For additional macOS packages and installers, see [community-supported docs](docs/install_macos.md#community-unofficial)

[Linux & Unix](docs/install_linux.md)

- [Debian, Raspberry Pi, Ubuntu](docs/install_linux.md#debian) - [Amazon Linux, CentOS, Fedora, openSUSE, RHEL, SUSE](docs/install_linux.md#rpm) - [Precompiled binaries](docs/install_linux.md#precompiled-binaries) on [releases page][]

For additional Linux & Unix packages and installers, see [community-supported docs](docs/install_linux.md#community-unofficial)

[Windows](docs/install_windows.md)

- [WinGet](docs/install_windows.md#winget) - [Precompiled binaries](docs/install_windows.md#precompiled-binaries) on [releases page][]

For additional Windows packages and installers, see [community-supported docs](docs/install_windows.md#community-unofficial)

Build from source

See here on how to [build GitHub CLI from source](docs/install_source.md).

GitHub Codespaces

To add GitHub CLI to your codespace, add the following to your [devcontainer file](https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file):

"features": {
  "ghcr.io/devcontainers/features/github-cli:1": {}
}

GitHub Actions

[GitHub-hosted runners](https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners) have the GitHub CLI pre-installed, which is updated weekly.

If a specific version is needed, your GitHub Actions workflow will need to install it based on the [macOS](#macos), [Linux & Unix](#linux--unix), or [Windows](#windows) instructions above.

For information on all pre-installed tools, see [`actions/runner-images`](https://github.com/actions/runner-images)

Verification of binaries

Starting with v2.93.0, releases of `gh` are published as immutable releases. For more information, see [Immutable releases](https://docs.github.com/en/code-security/concepts/supply-chain-security/immutable-releases).

Since version 2.50.0, `gh` has been producing [Build Provenance Attestation](https://github.blog/changelog/2024-06-25-artifact-attestations-is-generally-available/), enabling a cryptographically verifiable paper-trail back to the origin GitHub repository, git revision, and build instructions used. The build provenance attestations are signed and rely on Public Good [Sigstore](https://www.sigstore.dev/) for PKI.

There are two common ways to verify a downloaded release, depending on whether `gh` is already installed or not. If `gh` is installed, it's trivial to verify a new release:

- **Option 1: Using `gh` if already installed:**

  $ gh at verify -R cli/cli gh_2.62.0_macOS_arm64.zip
  Loaded digest sha256:fdb77f31b8a6dd23c3fd858758d692a45f7fc76383e37d475bdcae038df92afc for file://gh_2.62.0_macOS_arm64.zip
  Loaded 1 attestation from GitHub API
  ✓ Verification succeeded!

  sha256:fdb77f31b8a6dd23c3fd858758d692a45f7fc76383e37d475bdcae038df92afc was attested by:
  REPO     PREDICATE_TYPE                  WORKFLOW
  cli/cli  https://slsa.dev/provenance/v1  .github/workflows/deployment.yml@refs/heads/trunk

- **Option 2: Using Sigstore [`cosign`](https://github.com/sigstore/cosign):**

To perform this, download the [attestation](https://github.com/cli/cli/attestations) for the downloaded release and use cosign to verify the authenticity of the downloaded release:

  $ cosign verify-blob-attestation --bundle cli-cli-attestation-3120304.sigstore.json \
        --new-bundle-format \
        --certificate-oidc-issuer="https://token.actions.githubusercontent.com" \
        --certificate-identity="https://github.com/cli/cli/.github/workflows/deployment.yml@refs/heads/trunk" \
        gh_2.62.0_macOS_arm64.zip
  Verified OK

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 122 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # GitHub CLI
  2. GitHub CLI, or the gh CLI, is GitHub on the command line. It brings pull requests, issues, and other GitHub concepts to the terminal next to where you are already working with `git` and your code.
  3. > [!IMPORTANT]
  4. > GitHub CLI's PGP signing key rotation for Linux package repositories is effective September 5, 2026; users experiencing package installation or update problems can find solutions in the [public announcement](https://github.com/cli/cli/issues/13118).
  5. ![screenshot of gh pr status](https://user-images.githubusercontent.com/98482/84171218-327e7a80-aa40-11ea-8cd1-5177fc2d0e72.png)
  6. GitHub CLI is supported for users on GitHub.com, GitHub Enterprise Cloud, and [supported GitHub Enterprise Server versions](https://docs.github.com/en/enterprise-server/admin/all-releases), with support for macOS, Windows, and Linux.
  7. ## Documentation
  8. For [installation options see below](#installation), for usage instructions [see the manual](https://cli.github.com/manual/).
  9. ## Agent skills
  10. An [agent skill](https://agentskills.io) is available for driving `gh` from coding agents. Install or update it with the built-in `gh skill` command:
  11. ```shell
  12. # Install the skill (user scope recommended)
  13. gh skill install cli/cli gh --scope user
  14. # Update the skill after a `gh` release
  15. gh skill update gh
  16. ```
  17. ## Contributing
  18. If anything feels off or if you feel that some functionality is missing, please check out the [contributing page](.github/CONTRIBUTING.md). There you will find instructions for sharing your feedback, building the tool locally, and submitting pull requests to the project.
  19. If you are a hubber and are interested in shipping new commands for the CLI, check out our [doc on internal contributions](docs/working-with-us.md)
  20. <!-- this anchor is linked to from elsewhere, so avoid renaming it -->
  21. ## Installation
  22. ### [macOS](docs/install_macos.md)
  23. - [Homebrew](docs/install_macos.md#homebrew)
  24. - [Precompiled binaries](docs/install_macos.md#precompiled-binaries) on [releases page][]
  25. For additional macOS packages and installers, see [community-supported docs](docs/install_macos.md#community-unofficial)
  26. ### [Linux & Unix](docs/install_linux.md)
  27. - [Debian, Raspberry Pi, Ubuntu](docs/install_linux.md#debian)
  28. - [Amazon Linux, CentOS, Fedora, openSUSE, RHEL, SUSE](docs/install_linux.md#rpm)
  29. - [Precompiled binaries](docs/install_linux.md#precompiled-binaries) on [releases page][]
  30. For additional Linux & Unix packages and installers, see [community-supported docs](docs/install_linux.md#community-unofficial)
  31. ### [Windows](docs/install_windows.md)
  32. - [WinGet](docs/install_windows.md#winget)
  33. - [Precompiled binaries](docs/install_windows.md#precompiled-binaries) on [releases page][]
  34. For additional Windows packages and installers, see [community-supported docs](docs/install_windows.md#community-unofficial)
  35. ### Build from source
  36. See here on how to [build GitHub CLI from source](docs/install_source.md).
  37. ### GitHub Codespaces
  38. To add GitHub CLI to your codespace, add the following to your [devcontainer file](https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file):
  39. ```json
  40. "features": {
  41. "ghcr.io/devcontainers/features/github-cli:1": {}
  42. }
  43. ```
  44. ### GitHub Actions
  45. [GitHub-hosted runners](https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners) have the GitHub CLI pre-installed, which is updated weekly.
  46. If a specific version is needed, your GitHub Actions workflow will need to install it based on the [macOS](#macos), [Linux & Unix](#linux--unix), or [Windows](#windows) instructions above.
  47. For information on all pre-installed tools, see [`actions/runner-images`](https://github.com/actions/runner-images)
  48. ### Verification of binaries
  49. Starting with v2.93.0, releases of `gh` are published as immutable releases. For more information, see [Immutable releases](https://docs.github.com/en/code-security/concepts/supply-chain-security/immutable-releases).
  50. Since version 2.50.0, `gh` has been producing [Build Provenance Attestation](https://github.blog/changelog/2024-06-25-artifact-attestations-is-generally-available/), enabling a cryptographically verifiable paper-trail back to the origin GitHub repository, git revision, and build instructions used. The build provenance attestations are signed and rely on Public Good [Sigstore](https://www.sigstore.dev/) for PKI.
  51. There are two common ways to verify a downloaded release, depending on whether `gh` is already installed or not. If `gh` is installed, it's trivial to verify a new release:
  52. - **Option 1: Using `gh` if already installed:**
  53. ```shell
  54. $ gh at verify -R cli/cli gh_2.62.0_macOS_arm64.zip
  55. Loaded digest sha256:fdb77f31b8a6dd23c3fd858758d692a45f7fc76383e37d475bdcae038df92afc for file://gh_2.62.0_macOS_arm64.zip
  56. Loaded 1 attestation from GitHub API
  57. ✓ Verification succeeded!
  58. sha256:fdb77f31b8a6dd23c3fd858758d692a45f7fc76383e37d475bdcae038df92afc was attested by:
  59. REPO PREDICATE_TYPE WORKFLOW
  60. cli/cli https://slsa.dev/provenance/v1 .github/workflows/deployment.yml@refs/heads/trunk
  61. ```
  62. - **Option 2: Using Sigstore [`cosign`](https://github.com/sigstore/cosign):**
  63. To perform this, download the [attestation](https://github.com/cli/cli/attestations) for the downloaded release and use cosign to verify the authenticity of the downloaded release:
  64. ```shell
  65. $ cosign verify-blob-attestation --bundle cli-cli-attestation-3120304.sigstore.json \
  66. --new-bundle-format \
  67. --certificate-oidc-issuer="https://token.actions.githubusercontent.com" \
  68. --certificate-identity="https://github.com/cli/cli/.github/workflows/deployment.yml@refs/heads/trunk" \
  69. gh_2.62.0_macOS_arm64.zip
  70. Verified OK
  71. ```
  72. ## Comparison with hub
  73. For many years, [hub](https://github.com/github/hub) was the unofficial GitHub CLI tool. `gh` is a new project that helps us explore
  74. what an official GitHub CLI tool can look like with a fundamentally different design. While both
  75. tools bring GitHub to the terminal, `hub` behaves as a proxy to `git`, and `gh` is a standalone
  76. tool. Check out our [more detailed explanation](docs/gh-vs-hub.md) to learn more.
  77. [releases page]: https://github.com/cli/cli/releases/latest

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.