@mastra/corenpm
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 1.82.0
- last known licence Apache-2.0
- stars 29,441
- assessment attempted today
- GitHub evidence observed yesterday
- registry checked 24 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 30 checks
What the project says about itself
- Build provenance — the latest release, 1.82.0, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node >=22.13.0. Source: the registry.
- Publishers on the registry — 7. Source: the registry.
Third-party facts checked 4 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-10 | first verdict: active |
Supply-chain history 1
-
account hijacked 2026-06 1.42.1
An employee’s machine was compromised through a social-engineering link and 141 packages were republished with a dependency whose post-install script pulled a wallet-stealing trojan.
Removed; the project published an incident report.
Source: Aikido analysis and the Mastra incident report, 17 June 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/@mastra/core)Watch it
Get told when @mastra/core 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.