The CLI reference lists the commands by task. This page is generated from the development branch's help; run packslip pin --help for the options your installed version supports.

packslip pin

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

Flags

Trust

Exit status

CodeMeaning
0Printed the signer fingerprint
1Verification failed, the release has no signer fingerprint, or an input was unusable
2The command line is invalid

Examples

Print the fingerprint of a release you already trust

packslip pin packslip.sigstore.json