@mintlify/cli 4.1.64
PkgFire would stop this release from installing.·Checked 44 minutes ago·Published 19 November 2026
Why
-
blockRelease suspect
PkgFire reviewed this release when it was published and compared it with 4.1.63. It has the shape of a hijacked release. It stays blocked until the PkgFire operator has checked it; if you have checked it yourself, add the package to Always allow. Its code gained what 4.1.63's did not have: a long encoded blob (dist/build-Nkr-5oHQ.js, dist/cli-CpLHWklV.js). Its code calls api.github.com, github.com, which 4.1.63's code did not call.
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.1.66warn19 Nov 20264.1.65block19 Nov 20264.1.64block19 Nov 20264.1.63warn18 Nov 20264.1.62warn18 Nov 20264.1.61warn18 Nov 20264.1.60warn18 Nov 20264.1.59warn18 Nov 20264.1.58warn18 Nov 20264.1.57warn18 Nov 20264.1.56warn18 Nov 20264.1.55warn18 Nov 20264.1.54warn18 Nov 20264.1.53warn18 Nov 20264.1.52warn18 Nov 20264.1.51warn17 Nov 20264.1.50warn17 Nov 20264.1.49warn17 Nov 20264.1.48warn17 Nov 20264.1.47warn17 Nov 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.