dead-deps — what happened to your dependencies

Is feathers still maintained?

No — feathers stopped being maintained around January 2018. The same project continues under the name @feathersjs/feathers.

Status
No longer maintained
Last maintained
January 2018
Use instead
@feathersjs/feathers on npm
Succession
Renamed package
Drop-in
no — expect code changes
Confidence
high

What should I use instead of feathers?

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

How to migrate from feathers to @feathersjs/feathers

Follow the Buzzard migration guide: the core moves to @feathersjs/feathers, and the transport and client pieces become separate @feathersjs/* packages such as @feathersjs/express and @feathersjs/socketio. If you are jumping straight to v5, the v5 guide covers the later named-export change.

Why feathers is on this list

Feathers split into scoped packages with version 3 (Buzzard), and the unscoped feathers package stopped at 2.2.4 in January 2018. Its npm notice says Feathers v3 has moved to @feathersjs/feathers and links to the project's migration guide. The scoped packages are actively released; Feathers is now on v5.

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

feathers alternatives

Beyond the primary recommendation, these are credible for feathers's use case:

Check your own project for feathers

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

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