Compatibility and support

Packagers and teams that keep packslip at a fixed version can find what an unchanged binary keeps doing, what forces an update, and what each release is tested against. Publishers can find what to check before recommending packslip install. To install packslip, see Install packslip.

What an unchanged binary keeps doing

An older packslip can stay your bootstrapper while the tools it installs move on. Ordinary tool updates need no matching packslip release, because the version 1 format contract keeps release metadata stable. A new major version of the CLI, library, or action leaves the format at version 1. Maintaining packaged verifiers lists what can force an update.

Supported platforms

packslip install runs on Linux x64 and ARM64, macOS ARM64, and Windows x64 and ARM64. Elsewhere, Intel macOS included, it fails with unsupported bootstrap host <os>/<arch>, such as darwin/x86_64. verify and pin have no host check, so a source build that compiles there can run them. Check for a release build lists the release builds.

Every release must pass the install tests natively on those five platforms. It must also build and install the Debian and RPM packages from the offline source archive on Linux x64 and ARM64; see Package packslip for a distribution.

Version requirements

First packslip release with each feature:

Releases up to 1.10.1 differ from later ones:

Update packslip, the npm package, or the copied verifier to get the repository binding. Check what install supports lists how packslip install differs in those releases.

Other version differences:

The mise packslip: backend (Use packslip with mise) first shipped in mise 2026.9.2. Later releases added:

Verification matrix

Each release's tests run packslip 1.4.0 and the current verifier on the same inputs, and both must give these results:

The checked support claim covers only Sigstore bundle v0.3 and Rekor dsse/0.0.1 entries.

Trust-root lifetime and freshness

The trust-root tests refresh from a signed synthetic TUF repository with distinct keys and root versions 1, 2, and 3:

These tests establish rotation and failure behavior but do not replay the production Sigstore TUF repository's historical root chain. An old binary's install can catch up only while that repository keeps every intermediate root each transition needs.

Installing also needs an eligible release and current trust and list metadata. Age alone does not make a release ineligible: an installer test accepts a release published in 2020 when its list is fresh. Compatibility never makes packslip accept an expired list, a list sequence lower than one already accepted, or a release a security fix rejects; see Freshness and rollback protection.

Maintaining packaged verifiers

These can require a packslip update:

Upstream promises no fixed update cadence, maintenance horizon, or number of years an unchanged binary will work. It keeps verification and security fixes suitable for backporting to packaged verifiers. When a release breaks compatibility, its release notes name the affected versions, the format or test input, the reason, and the update or publisher change you need. A security rejection takes precedence over keeping a compatibility test passing.

Distributions decide which packaged packslip versions they maintain, with the verification matrix as evidence.

Check a tool's handoff

Every release must pass tests of how packslip install lays out and hands off a tool:

These tests do not establish that a tool's own setup and self-update work with the layout. Only mise has been checked by hand, on Linux x64 with packslip 1.5.1:

Other platform and scope combinations are unverified for mise's lifecycle.

Before you document packslip install for a tool on a new platform or scope:

  1. Record the tool's exact release and bundle digest, the platform, the scope, the packslip version, and the tree and command paths.
  2. In an isolated account, run the tool's normal command, setup, and self-update through the exported command.
  3. Check that runtime files beside the command survive and are found, that arguments and exit status pass through, and that setup uses the intended scope.
  4. Note whether self-update replaces the executable or its exported command. Record any shell or PATH changes the tool makes itself.
  5. After self-update, check that the exported command still works. Then reinstall through packslip and check that it handles the changed ownership, including conflicts and recovery.

A successful --version call establishes less than this check.