Every supported HitKeep binary and Docker image published in a GitHub Release is signed with a GitHub Artifact Attestation — a cryptographically verifiable build-provenance record linking the artifact to the exact commit, workflow run, and Actions runner that produced it.
Verifying before deployment gives you evidence that the artifact was built from the official source code and has not been tampered with in transit or in the registry.
Prerequisites
Section titled “Prerequisites”Install the GitHub CLI (gh) v2.49 or later, which includes the attestation subcommand:
gh --versionNo authentication is required for public repositories.
Verifying Binaries
Section titled “Verifying Binaries”HitKeep attaches raw Linux binaries to GitHub Releases for linux/amd64 and linux/arm64. Each binary is attested at build time and listed in the release SHA256SUMS file.
1. Download the binary:
# Linux AMD64curl -L https://github.com/HitKeep/hitkeep/releases/latest/download/hitkeep-linux-amd64 \ -o hitkeep-linux-amd64
# Linux ARM64curl -L https://github.com/HitKeep/hitkeep/releases/latest/download/hitkeep-linux-arm64 \ -o hitkeep-linux-arm642. Verify the attestation:
gh attestation verify hitkeep-linux-amd64 --repo HitKeep/hitkeep --signer-repo HitKeep/hitkeepgh attestation verify hitkeep-linux-arm64 --repo HitKeep/hitkeep --signer-repo HitKeep/hitkeepFor a build made after the transfer, a passing result looks like:
Loaded digest sha256:<digest> for file://hitkeep-linux-amd64✓ Verification succeeded!
The following 1 attestation(s) matched the artifact: - Build repo: https://github.com/HitKeep/hitkeep - Workflow: .github/workflows/pipeline.yml - Ref: refs/tags/v1.x.x - Signer: https://github.com/HitKeep/hitkeep/.github/workflows/pipeline.yml@refs/tags/v1.x.xIf verification fails for any reason the command exits with a non-zero status and prints a clear error. Do not run the binary.
3. Verify the checksum:
curl -L https://github.com/HitKeep/hitkeep/releases/latest/download/SHA256SUMS \ -o SHA256SUMSsha256sum -c --ignore-missing SHA256SUMSVerifying Docker Images
Section titled “Verifying Docker Images”HitKeep images are published to two registries for linux/amd64 and linux/arm64, both carrying identical provenance attestations.
Docker Hub
Section titled “Docker Hub”gh attestation verify oci://index.docker.io/pascalebeier/hitkeep:latest \--repo HitKeep/hitkeep --signer-repo HitKeep/hitkeepPin to a specific version (recommended for production):
gh attestation verify oci://index.docker.io/pascalebeier/hitkeep:2.17.0 \--repo HitKeep/hitkeep --signer-repo HitKeep/hitkeepGitHub Container Registry (GHCR)
Section titled “GitHub Container Registry (GHCR)”gh attestation verify oci://ghcr.io/hitkeep/hitkeep:latest \--repo HitKeep/hitkeep --signer-repo HitKeep/hitkeepWhat the Attestation Proves
Section titled “What the Attestation Proves”| Claim | What it means |
|---|---|
| Repository | Built from HitKeep/hitkeep, or PascaleBeier/hitkeep before the transfer |
| Workflow | Produced by .github/workflows/pipeline.yml |
| Ref | Corresponds to a specific tag or commit |
| Runner environment | Ran on a GitHub-hosted ubuntu-latest runner |
The attestation does not prove that the binary is free of vulnerabilities — it proves the artifact originated from the official CI pipeline and has not been modified after the fact.