packslip pin
- Usage:
packslip pin [FLAGS] <BUNDLE>
Verify a release bundle and print its signer fingerprint
The fingerprint, ps1_ and 26 characters, comes from the forge's issuer and the signing repository's ID. It stays the same when the repository is renamed, moves to another owner, or signs from another workflow; a repository that later takes the old name gets a different one. Only a keyless release whose certificate records a repository ID has one; a key-signed release is pinned by its key, with packslip verify --pubkey.
Verification works as in packslip verify without --allow-other-repository. A domain project, one named after a host such as mytool.example.com, has no policy from its name, so pass --issuer with --identity or --identity-prefix. Only the fingerprint is printed, on stdout.
Run pin on a release you already trust, since it fingerprints whichever repository signed. Publish the value where consumers can read it without trusting a release, such as a README, and check releases with packslip verify --pin or packslip install --pin. See https://packslip.dev/docs/verifying/#pin-a-signer-with-its-fingerprint
Arguments
<BUNDLE>— Local release bundle to verify and fingerprint
Flags
-h --help— Print help
Trust
--identity <IDENTITY>— Require this exact certificate identity, ref included, such as https://github.com/owner/repo/.github/workflows/release.yml@refs/tags/v1.2.3A GitHub or GitLab repository name in it matches in any case; the rest matches exactly. For a domain project, also pass --issuer, or a certificate from any issuer is accepted.
--identity-prefix <IDENTITY_PREFIX>— Require a certificate identity that starts with this prefix, such as https://github.com/owner/repo/A GitHub or GitLab repository name in it matches in any case; the rest matches exactly. For a domain project, also pass --issuer, or a certificate from any issuer is accepted.
--issuer <ISSUER>— Require this OIDC issuer; for a domain project it alone accepts any signer from that issuer, so pair it with --identity or --identity-prefix--allow-unlogged— Accept a bundle without a transparency log entry--trusted-root <TRUSTED_ROOT>— Use this Sigstore trusted_root.json instead of the embedded one
Exit status
| Code | Meaning |
|---|---|
0 | Printed the signer fingerprint |
1 | Verification failed, the release has no signer fingerprint, or an input was unusable |
2 | The command line is invalid |
Examples
Print the fingerprint of a release you already trust
packslip pin packslip.sigstore.json