dead-deps — what happened to your dependencies

Is event-stream still maintained?

No — event-stream stopped being maintained around November 2018. No single package succeeded event-stream; the fix depends on what you were using it for.

Status
No longer maintained
Last maintained
November 2018
Use instead
Nothing directly — remove the dependency
Succession
Replacement project
Drop-in
not applicable
Confidence
medium

What replaced event-stream?

No single package succeeded event-stream; the fix depends on what you were using it for. There is nothing to swap in, so plan the change rather than the upgrade.

Getting off event-stream

es.split() maps to split2, es.map and es.through map to through2, es.merge maps to merge-stream, and es.pipeline maps to require('node:stream').pipeline.

Why event-stream is on this list

The event-stream repository was archived on 28 November 2018, after a handover to a new maintainer resulted in a malicious dependency, flatmap-stream, being pulled into the 3.3.6 release. The current 4.0.1 release, published in September 2018, does not depend on it, but the project has had no activity since. No single package replaced it; the pieces it bundled now live in small focused modules and in Node's own stream helpers.

The succession is well supported, but it is not the only defensible choice.

event-stream alternatives

Beyond the primary recommendation, these are credible for event-stream's use case:

Check your own project for event-stream

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

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