@mintlify/scraping 4.0.1204
PkgFire would install this release with a warning.·Checked 4 hours ago·Published 29 October 2026
Why
-
warnRelease cooldown
Published 2 days 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
- None, and no earlier version had any
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
4.0.1212warn30 Oct 20264.0.1211warn30 Oct 20264.0.1210warn30 Oct 20264.0.1208warn30 Oct 20264.0.1207warn30 Oct 20264.0.1206warn29 Oct 20264.0.1205warn29 Oct 20264.0.1204warn29 Oct 20264.0.1203warn29 Oct 20264.0.1202warn29 Oct 20264.0.1201warn29 Oct 20264.0.1200warn29 Oct 20264.0.1199warn29 Oct 20264.0.1198warn28 Oct 20264.0.1197warn28 Oct 20264.0.1196warn28 Oct 20264.0.1195warn28 Oct 20264.0.1194warn28 Oct 20264.0.1193warn27 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.