@vercel/container 26.1.0
PkgFire would stop this release from installing.·Checked 1 hour ago·Published 18 November 2026
Why
-
blockProvenance lost
This version was published without build provenance, but 0.1.0 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 0.1.0 had it
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
26.1.0block18 Nov 202626.0.1block17 Nov 202626.0.0block13 Nov 202625.0.3block12 Nov 202625.0.2block9 Nov 202625.0.1block6 Nov 202625.0.0block5 Nov 202624.0.1block31 Oct 202624.0.0block29 Oct 202623.0.2block28 Oct 202623.0.1block28 Oct 202623.0.0block27 Oct 202622.0.2warn23 Oct 202622.0.1warn22 Oct 2026
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.