@mintlify/common 1.0.1320
PkgFire would install this release with a warning.·Checked 10 minutes ago·Published 28 October 2026
Why
-
warnSuspicious behaviour
Detects access to sensitive files (credentials, configs, keys)
-
warnSuspicious behaviour
Detects unicode homoglyphs and uncommon characters used for obfuscation
-
warnRelease cooldown
Published 3 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
1.0.1333warn30 Oct 20261.0.1332warn30 Oct 20261.0.1331warn30 Oct 20261.0.1330warn30 Oct 20261.0.1329warn30 Oct 20261.0.1328warn29 Oct 20261.0.1327warn29 Oct 20261.0.1326warn29 Oct 20261.0.1325warn29 Oct 20261.0.1324warn29 Oct 20261.0.1323warn29 Oct 20261.0.1322warn29 Oct 20261.0.1321warn29 Oct 20261.0.1320warn28 Oct 20261.0.1319warn28 Oct 20261.0.1318warn28 Oct 20261.0.1317warn28 Oct 20261.0.1316warn28 Oct 20261.0.1315warn27 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.