@mistralai/mistralai 3.4.0
PkgFire would install this release with a warning.·Checked 4 hours ago·Published 28 October 2026
Why
-
warnSuspicious behaviour
Detects access to sensitive files (credentials, configs, keys)
-
warnSuspicious behaviour
Possible credential in the published package: generic-api-key
-
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
- Attested · source commit ↗
Licence and upkeep
- Licence
- Apache-2.0
- Source
- github.com/mistralai/client-ts ↗
- OpenSSF Scorecard
- None published for this repository, which is common for small projects and not the same as scoring badly
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.
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.