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 →Loading historical repository activity…
Signals · last 2 checks
Dated reporting about this package. These events are separate from its current maintenance score.
· npm
Nx described how a GitHub Actions injection exposed a publishing token and enabled malicious releases that collected sensitive files. Its response included trusted publishing and manual release approval.
Affected versions: See Nx’s linked advisory for the package-specific affected versions.
Packages: nx
Source: Nx maintainers
Third-party facts checked today; registry facts on every crawl.
| When | Change |
|---|---|
| 2026-09-05 | first verdict: active |
account hijacked 2025-08 20.9.0–20.12.0, 21.5.0–21.8.0
A pull-request title injection in a GitHub Actions workflow leaked a token that triggered the publish pipeline; the published nx and @nx/* versions ran a post-install script that used local AI CLIs to hunt for secrets and pushed them to public repositories.
Removed after about four hours; npm revoked the tokens; Nx moved to trusted publishing with manual approval.
Source: Nx post-mortem "s1ngularity", 5 September 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/nx)Watch it
Get told when nx 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.