packslip verify
- Usage:
packslip verify [FLAGS] <BUNDLE>
Verify a release bundle or release list, and downloaded files
Check the signature, the transparency log entry, and the statement. Each --artifact file is checked against its signed digest, and an artifact also against its signed size. Nothing is downloaded.
A github.com or gitlab.com project's name sets the policy. It requires the forge's issuer and a certificate whose source repository is the project's, or, if the certificate records none, a signer that is a workflow of the project's repository. A reusable workflow the project calls may therefore sign. --issuer, --identity, and --identity-prefix narrow that policy and never replace it. A domain project, one named after a host such as mytool.example.com, has no such policy, so pass --issuer with --identity, --identity-prefix, --source-repository, or --pin. --pubkey verifies a key-signed release instead. --source-repository and --pin add checks, and --allow-other-repository accepts a signer outside the project's repository, such as a repackager's.
Then check that the verified project and version are the ones you meant. A release list's expiry and sequence are not checked. See https://packslip.dev/docs/verifying/
Arguments
<BUNDLE>— Local release bundle or signed release list to verify
Flags
-a --artifact <ARTIFACT>— A downloaded artifact or resource asset to check against its signed digest, and an artifact also against its size (repeatable)Files are matched by name, so keep the name each was published under. A release list has no artifacts to check.
-h --help— Print help
Trust
-p --pubkey <PUBKEY>— Require this public key: a minisign .pub file, such as one frompackslip keygen, or its base64 lineConflicts with every other trust flag except --allow-unlogged and --trusted-root.
--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, --identity-prefix, --source-repository, or --pin--source-repository <SOURCE_REPOSITORY>— Require the certificate to record this source repository, such as https://github.com/owner/repo, whichever workflow signedUnlike an identity prefix of the repository, it also matches a reusable workflow of another repository that the repository's run called. A GitHub or GitLab repository name in it matches in any case. Needs --issuer. Conflicts with --identity and --identity-prefix.
--pin <PIN>— Require this signer fingerprint (ps1_...), aspackslip pinprints it--allow-other-repository— Accept a keyless signer outside the project's repository, such as a repackager'sFor a github.com or gitlab.com project. Needs --issuer and one of --identity, --identity-prefix, or --source-repository to name the signer. Conflicts with --pubkey.
--allow-unlogged— Accept a bundle without a transparency log entry, such as one created with --key --no-log--trusted-root <TRUSTED_ROOT>— Use this Sigstore trusted_root.json instead of the embedded one
Output
-J --json— Print the verified report as JSONThe report lists every artifact with its signed digest, and source_repository when the signing certificate records one. For a release list, the verified list statement is printed instead.
Exit status
| Code | Meaning |
|---|---|
0 | The bundle verified, and every --artifact matched it |
1 | Verification failed, or an input was unusable: a file could not be read, a key or fingerprint is malformed, or the trust flags conflict or are missing |
2 | The command line is invalid |
Examples
Verify a GitHub release and a downloaded artifact
packslip verify packslip.sigstore.json \
--artifact mytool-1.2.3-linux-x64.tar.gz
Verify hk 2.8.0 against its signer fingerprint
packslip verify packslip.sigstore.json \
--pin ps1_snirenkjwr7m5ozgcufameodnm \
--artifact hk-x86_64-unknown-linux-gnu.tar.gz
Verify a release a repackager signed from its own repository
packslip verify packslip.sigstore.json \
--issuer https://token.actions.githubusercontent.com \
--identity-prefix https://github.com/repackager/mytool/ \
--allow-other-repository
Verify a key-signed release
packslip verify packslip.sigstore.json \
--pubkey release.pub \
--artifact mytool-1.2.3-linux-x64.tar.gz