dead-deps — what happened to your dependencies

Is node-uuid still maintained?

No — node-uuid stopped being maintained around March 2017. The same project continues under the name uuid.

Status
No longer maintained
Last maintained
March 2017
Use instead
uuid — on npm
Succession
Renamed package
Drop-in
no — expect code changes
Confidence
high

What should I use instead of node-uuid?

The same project continues under the name uuid. uuid is not a drop-in replacement, so expect to change call sites.

How to migrate from node-uuid to uuid

Install uuid and switch from uuid.v4() on a default export to import { v4 as uuidv4 } from 'uuid'.

Why node-uuid is on this list

node-uuid was renamed to uuid in 2017, and the old package carries an npm deprecation notice reading "Use uuid module instead". Its final release, 1.4.8, is a shim published in March 2017. uuid is actively maintained and has moved to named, ESM-friendly exports since the rename.

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

node-uuid alternatives

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

Check your own project for node-uuid

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

Run that in the directory holding your lockfile. If node-uuid 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.