Packagist plans to store and sign every Composer package itself
Most PHP packages today have no reliable checksum because Composer installs a zip GitHub regenerates on demand. Alpha-Omega funding will have Packagist store, checksum and sign artifacts instead.
Packagist published a five-phase plan on 12 November to stop treating package archives as someone else’s problem. Right now Packagist hosts only metadata, and Composer installs a zip that GitHub, GitLab or Bitbucket generates on the fly from the git tag. Composer can verify a checksum against that zip, but in practice it has to be left empty for most packages, because the archive isn’t stable enough to pin one.
The plan, funded by Alpha-Omega, starts with Packagist downloading and permanently storing the artifact for every version itself, with a checksum published in the metadata and a public transparency log. Later phases add a Sigstore signature and build provenance attestation per artifact, API tokens scoped to specific packages that expire and auto-revoke if leaked in public, Trusted Publishing so CI exchanges an OIDC token for a short-lived credential instead of storing a long-lived secret, and a composer publish command for staged, hardware-key-approved releases. Packagist has already added FIDO2 hardware key support as a second authentication factor.
Why it matters: every composer install today pulls an unpinned, unsigned snapshot that two different servers could in principle serve differently. This closes that gap the same way Sigstore and provenance attestations have started closing it for npm and PyPI.
The caveat: this is a roadmap, not a shipped feature. Packagist says it’s still in the planning stage for phase one; there’s no date yet for when checksums, signing or Trusted Publishing actually land.