Describe the feature or problem you’d like to solve
The instructions in https://docs.github.com/en/actions/how-tos/secure-your-work/use-artifact-attestations/verify-attestations-offline:
gh attestation download PATH/TO/YOUR/BUILD/ARTIFACT-BINARY -R ORGANIZATION_NAME/REPOSITORY_NAME
require a valid GH_TOKEN or gh auth login. That complicates using it to verify attestations.
It would be great if GitHub attestations were adopted widely, and user friction doesn't help.
Proposed solution
Treat attestations as public for public projects. That benefits the CLI and its users because simplifying adoption improves supply chain security for everybody.
Additional context
This is part of a bigger review at https://github.com/diskuv/dk/blob/V2_4/docs/posts/2025-10-24-overview-ci-attestations.md
Describe the feature or problem you’d like to solve
The instructions in https://docs.github.com/en/actions/how-tos/secure-your-work/use-artifact-attestations/verify-attestations-offline:
require a valid
GH_TOKENorgh auth login. That complicates using it to verify attestations.It would be great if GitHub attestations were adopted widely, and user friction doesn't help.
Proposed solution
Treat attestations as public for public projects. That benefits the CLI and its users because simplifying adoption improves supply chain security for everybody.
Additional context
This is part of a bigger review at https://github.com/diskuv/dk/blob/V2_4/docs/posts/2025-10-24-overview-ci-attestations.md