@pkgr/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 0.3.6
- last known licence MIT
- stars 13
- assessment attempted today
- GitHub evidence observed today
- 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 11 checks
What the project says about itself
- Build provenance — the latest release, 0.3.6, carries a signed provenance attestation. Source: the registry.
- Supported runtime — node ^14.18.0 || >=16.0.0. Source: the registry.
- Publishers on the registry — 1. Source: the registry.
- Funding — opencollective.com/pkgr. Source: the registry.
Third-party facts checked today; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-12 | first verdict: active |
Supply-chain history 1
-
account hijacked 2025-07 0.2.8
The maintainer was phished through the look-alike domain npnjs.com and the stolen token published versions whose install script loaded a Windows trojan.
Tokens revoked and the versions deprecated and removed within hours; CVE-2025-54313.
Source: Socket and Snyk analyses, 19–22 July 2025. 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/@pkgr/core)Watch it
Get told when @pkgr/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.