@mistralai/mistralainpm
This package has dated incident reports relevant to its trust history. Check the affected releases and the response before drawing conclusions about its current version.
Read the incident coverage →- latest 2.7.0
- last known licence Apache-2.0
- stars 157
- assessment attempted 29 days ago
- registry checked 25 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Maintenance trends
Loading historical repository activity…
Signals · last 10 checks
What the project says about itself
- Build provenance — the latest release, 2.7.0, carries a signed provenance attestation. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
Third-party facts checked 29 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-12 | first verdict: active |
Supply-chain history 1
-
account hijacked 2026-05 2.2.2–2.2.4
Compromised tarballs gained a root router_init.js and a GitHub-hosted dependency whose prepare script ran a credential stealer that spread through stolen npm tokens.
Removed; valid provenance did not help, because the code ran inside the trusted workflow.
Source: Aikido analysis, 12 May 2026. History, not a warning about today — the verdict above is about maintenance now.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@mistralai/mistralai)Watch it
Get told when @mistralai/mistralai changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.