Grepedia
PA

packslip

Packslip is a tool for publishing signed, platform-aware release manifests that enable secure, verifiable, and automated software installations.

Score0
About

Packslip is a secure release management system that provides signed manifests for software releases. Created by Jeff Dickey (author of mise) and Shunsuke Suzuki (author of aqua), it allows developers to publish signed release bundles that consumers can verify against a trusted identity or key. By using packslip, maintainers can provide installers, package managers, and users with the ability to verify downloads without relying on fragile "curl | sh" scripts, which are susceptible to tampering.

Functionality includes describing releases once with signed digests, supported platforms, and executable paths, which enables installers to automatically select and verify the correct download for the user's platform. Packslip uses the in-toto statement format inside a Sigstore bundle, meaning publishers do not necessarily need to manage long-lived signing keys if they use a supported CI system with OIDC identity support.

Some of the key features are:

  • Signed Manifests: Packages release metadata, including file digests, into a tamper-proof Sigstore bundle.
  • Keyless Signing: Supports OIDC-based signing in CI environments like GitHub Actions, removing the need to manage secret keys.
  • Platform-Aware Installation: Metadata describes which OS, architecture, and libc are required, allowing for automated platform-specific artifact selection.
  • Executable Path Declaration: Explicitly defines executable paths and command names for secure exporting to user directories.
  • Security Provenance: Integrates with build provenance and transparency logs to provide verifiable evidence of a release's origin.
  • Resource Management: Facilitates the shipping of supplementary files such as man pages, shell completions, and SBOMs alongside main binaries.
  • Tool Pinning: Provides signer fingerprints to allow users to establish trust before the first install.

Packslip functions by integrating into existing release pipelines. When a project builds its release artifacts, the packslip action or CLI generates a signed bundle (packslip.sigstore.json) that resides alongside the release binaries. Installers use the packslip CLI to discover, fetch, and verify this bundle against a pinned identity or public key. If the signature and digests are valid, the installer exports the declared commands to a local bin directory, ensuring the binary is exactly what the publisher released.

Some common use cases include:

  • Secure Upstream Distribution: Providing a secure, verified way for users to install CLI tools without vulnerable shell piping.
  • Reproducible Installs: Ensuring that users always download the exact, intended version of a binary with verified hash integrity.
  • Platform-Specific Delivery: Packaging multiple architecture builds under one project name so users can "packslip install" a single command that automatically picks the right file.
  • Automated CI Bootstrap: Installing tools in CI/CD pipelines with high assurance, using signer pinning to prevent supply chain attacks.