expo-linking 56.0.19
PkgFire would install this release with a warning.·Checked 10 hours ago·Published 21 October 2026
Why
-
warnProvenance lost
This version was published without build provenance, but 58.0.13 was published with it. Provenance is produced by the repository's CI identity rather than by the token used to publish, so an attacker holding a stolen publishing token can release a version and cannot attest it. A maintainer who changed their release workflow produces the same pattern, so confirm which one this is before acting.
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Verified against the registry's key
- Build provenance
- None, though 58.0.13 had it
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.