@clerk/backend 3.31.2
PkgFire would install this release with a warning.·Checked 1 hour ago·Published 19 November 2026
Why
-
warnRelease cooldown
Published less than an hour ago, inside the 7-day cooldown. Most malicious releases are pulled within hours of publication, so a version this new has not yet had time to be caught.
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
- Attested · source commit ↗
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
3.31.2warn19 Nov 20263.31.1warn18 Nov 20263.31.0warn18 Nov 20263.30.0warn17 Nov 20263.29.0warn14 Nov 20263.28.0warn12 Nov 20262.33.9allow11 Nov 20263.27.0allow5 Nov 20263.26.6allow3 Nov 20263.26.5allow30 Oct 20263.26.4allow27 Oct 20263.26.3allow26 Oct 20263.26.2allow23 Oct 20263.26.1allow21 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.