Please use a private GitHub security advisory to report potential security vulnerabilities. Do not disclose exploit details, credentials, or private findings in a public issue. Ordinary non-sensitive bugs and documentation errors can be filed in GitHub Issues.

This project publishes a container image wrapping the upstream GitHub CLI. When reporting a suspected issue, identify the affected image tag or digest, platform/architecture, and reproduction details privately where possible.

These statements reflect the workflows and scripts in this repository, reviewed 2026-10-14. They describe what the automation is configured to do, not a guarantee that a specific registry tag has been rebuilt successfully or that a particular issue is fixed.

• The Dockerfile builds on Alpine (currently alpine:3.24.1) and runs apk upgrade --no-cache in both build stages. A new build can pick up then-available Alpine package fixes.
• Build and Release is scheduled daily, and publishes current rolling image tags when a build succeeds; additional builds run on pushes and manual dispatch. Upstream gh release resolution is implemented in hooks/scripts/set_tags.
• latest and the rolling major tag (e.g. v2) track the current upstream gh release and are rebuilt by the regular pipeline. vMAJOR.MINOR (e.g. v2.95) is a rolling tag only while that minor version is the latest upstream release line. When upstream moves to a later minor, the older minor tag is no longer refreshed by the daily workflow. Do not treat an old minor tag as an indefinitely patched release channel.
• Exact vX.Y.Z tags are left unchanged by default; an exception is the weekly refresh job, which rebuilds the three most recent upstream stable releases by default, republishing their exact tags on the updated base. The count can be changed by manual dispatch. Older exact tags do not get automatic fixes.
• An image already pulled or running does not update itself when the registry tag changes. Consumers must repull/redeploy (subject to their deployment system and pull policy). For reproducibility and supply-chain control, prefer digest pinning and deliberate review of updates; digest-pinned images do not auto-update.
• Trivy runs on pull requests, on a weekly schedule, and by manual dispatch. A HIGH/CRITICAL scan of all fixable package types is informational; an additional HIGH/CRITICAL fixable OS-package-only check is a failing gate. Hadolint and ShellCheck are configured separately. A passing gate does not prove absence of vulnerabilities.
• The downstream usage report describes publicly observable image references, not verified CVE exposure or which deployments have received an update.

The following conclusions originate from 2026-06-19; the current upstream advisories have been rechecked as of 2026-10-14 below, but the actual published Docker image digests have not been freshly rescanned as part of this documentation audit. Use recent Trivy output, upstream advisories, Alpine security notices, and the exact image digest under investigation before drawing deployment-specific conclusions.

These are source-advisory checks, not a current scan of every published tag/digest, installed package, or runtime configuration.

• CVE-2025-15558: Docker's upstream advisory confirms that this Docker CLI plugin-discovery issue is Windows-specific and explicitly states that non-Windows binaries are not impacted. The project's Linux-only image is therefore not affected by this particular Windows attack path; the existing OpenVEX statement records that assessment. This does not mean the upstream gh binary has no other vulnerabilities.
• CVE-2025-60876: Alpine's public tracker currently marks busybox 1.37.0-r31 in 3.24-main as possibly vulnerable. Do not infer it was fixed by an apk upgrade, nor assert that every deployed image digest contains that exact package version. Check package inventory for the specific image digest and its latest scanner results when assessing exposure.

The Alpine wording above is a tracker status, not an exploitability determination for this container. A change in upstream tracking or published image contents should trigger re-evaluation.

The project cannot patch vulnerabilities in the prebuilt upstream gh binary in this repository without moving to a patched upstream release. OS package findings depend on Alpine's available fixes. Both require rechecking the actually published image rather than extrapolating from an old report.

Where supported, scan consumers can supply the published OpenVEX statement:

trivy image --vex openvex.json maniator/gh:latest

The statement records a specific historical applicability assessment, not an assurance that every current scanner finding is harmless or fixed.