@rspack/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 2.3.2
- last known licence MIT
- stars 12,974
- assessment attempted yesterday
- GitHub evidence observed yesterday
- registry checked 26 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, 2.3.2, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node ^20.19.0 || >=22.12.0. Source: the registry.
- Publishers on the registry — 2. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — 1.4.0 4/4 done. Source: the repository's milestones.
Third-party facts checked 5 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-10 | first verdict: active |
Supply-chain history 1
-
account hijacked 2024-12 1.1.7
A stolen npm token published a version carrying an obfuscated Monero miner.
Deprecated, tokens reset, 1.1.8 released clean.
Source: Sonatype analysis, 20 December 2024. 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/@rspack/core)Watch it
Get told when @rspack/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.