dead-deps — what happened to your dependencies

Is eslint-plugin-node still maintained?

No — eslint-plugin-node stopped being maintained around March 2020. eslint-plugin-n is a community fork that picked eslint-plugin-node up and carried it on.

Status
No longer maintained
Last maintained
March 2020
Use instead
eslint-plugin-n on npm
Succession
Maintained fork
Drop-in
yes — swap the import
Confidence
high

Is there a maintained fork of eslint-plugin-node?

eslint-plugin-n is a community fork that picked eslint-plugin-node up and carried it on. eslint-plugin-n is close enough to a drop-in replacement that most projects only change the dependency and the import.

How to migrate from eslint-plugin-node to eslint-plugin-n

Swap the dependency, then change plugin:node/recommended to plugin:n/recommended and any node/ rule prefixes to n/.

Why eslint-plugin-node is on this list

eslint-plugin-node's README states that the project is no longer maintained and points readers at eslint-plugin-n; its last release was 11.1.0 in March 2020. eslint-plugin-n is the ESLint Community fork of that exact version, and it supports current ESLint releases and flat config. Rule names are identical apart from the plugin prefix.

The succession is settled: primary sources agree and the ecosystem has already moved.

eslint-plugin-node alternatives

The dataset lists no second option: eslint-plugin-n is where the ecosystem went, and nothing else has meaningful adoption.

Check your own project for eslint-plugin-node

npx dead-deps --all --min-state unmaintained

Run that in the directory holding your lockfile. If eslint-plugin-node is anywhere in your tree — a direct dependency or buried under something else — it appears in the report with this verdict, this successor and the same evidence links, alongside anything else that has stopped moving. Nothing is uploaded; the scan reads your lockfile locally and queries public registry metadata.

Exit code 1 means something was flagged, which makes npx dead-deps --min-state deprecated usable as a CI gate. See how verdicts are produced.

Evidence

Every claim on this page traces to a primary source. Check them:

See the full index of covered packages, or read the methodology for how a verdict is reached and why a quiet package is not a dead one.