dead-deps — what happened to your dependencies

Is socket.io-redis still maintained?

No — socket.io-redis stopped being maintained around May 2021. The same project continues under the name @socket.io/redis-adapter.

Status
No longer maintained
Last maintained
May 2021
Use instead
@socket.io/redis-adapter on npm
Succession
Renamed package
Drop-in
no — expect code changes
Confidence
high

What should I use instead of socket.io-redis?

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

How to migrate from socket.io-redis to @socket.io/redis-adapter

The default export became the named export createAdapter, and the adapter no longer creates Redis clients for you: build your own pubClient and subClient with redis or ioredis and pass them as createAdapter(pubClient, subClient).

Why socket.io-redis is on this list

The Redis adapter for Socket.IO was republished under the @socket.io scope at version 7, and the old socket.io-redis package stopped at 6.1.1 in May 2021. Its npm notice names @socket.io/redis-adapter and links to the official migration guide. The scoped adapter is the one documented on socket.io.

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

socket.io-redis alternatives

Beyond the primary recommendation, these are credible for socket.io-redis's use case:

Check your own project for socket.io-redis

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

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