GitHub CLI

Why it's ranked here

It ranks highly because it is the officially maintained bridge between the terminal and GitHub's own API, not a community wrapper. Releases carry cryptographically signed build provenance attestations verified through Sigstore, the codebase is MIT licensed, and the project ships an installable skill so coding agents can drive it directly rather than shelling out blind. That combination of trust, license, and agent readiness is rare for a CLI this central to daily development.

What's good

The API layer is deliberately careful: request options let a command opt out of following redirects so a delete on a renamed resource cannot silently downgrade into a harmless-looking GET. Every command that emits structured data supports JSON output with field selection and a query template, so scripts get stable fields independent of the human-readable view. Enterprise requests automatically disable telemetry, and authentication tokens are injected per host rather than hardcoded, so one login works across GitHub.com, Enterprise Cloud, and enterprise server instances.

Tradeoffs

Three top-level packages the project's own layout doc labels deprecated, one for git remotes, one for older tests, one for table printing, are still present rather than removed, a sign of incomplete internal cleanup. Its acceptance test suite creates and modifies real GitHub resources, so it cannot run against a sandbox and needs a dedicated authorized account. Outside contributors also face a formal gate: unsolicited pull requests are turned away unless an issue already carries explicit maintainer sign-off.

How to use it well

This fits engineers who already live in the terminal and want pull requests, issue triage, and workflow runs scriptable from the same shell as git, piping JSON output into other tools instead of parsing a web page. Coding agents can install the companion skill to drive it directly rather than guessing at flags. It is not a replacement for a GitHub API client embedded in an application, and it offers nothing for code hosted outside GitHub or GitHub Enterprise Server.

Observed

License

MIT

Language

Go

Interface

Command-line only; internally calls GitHub's REST and GraphQL APIs but exposes no public library or HTTP API of its own

Platform support

macOS, Windows, and Linux/Unix, plus GitHub Codespaces via a devcontainer feature

Hosting support

GitHub.com, GitHub Enterprise Cloud, and supported GitHub Enterprise Server versions

Authentication mechanism

Installs itself as a per-host git credential helper so ordinary git commands reuse the CLI's stored token

Request safety

A dedicated request option can disable HTTP redirect following, preventing Go's default policy from turning a DELETE into a GET on redirect

Structured output

Commands support JSON output with field selection and a query template, independent of the human-readable view

Release verification

Release binaries carry signed build provenance attestations, checkable through Sigstore

Deprecated internal packages

The project's own layout documentation marks the context, test, and utils top-level packages as deprecated

Contribution policy

External upstream pull requests require a tracked issue with both a help-wanted label and explicit acceptance criteria before implementation starts