Is event-stream healthy, maintained, and safe?

The verdict

OSPulse scores event-stream at 3/100 (critical risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. No — event-stream carries 1 unpatched critical advisory and should not be adopted without a remediation plan.

The last sign of life was 29 September 2018, more than 7 years ago (2860 days); by any practical measure the package looks abandoned. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. Ownership rests on a single maintainer — a bus-factor of one, meaning one person's availability is a single point of failure for everyone downstream.

OSV lists 1 known advisory for event-stream, including 1 critical. Open critical advisories are the strongest possible signal to pin to a patched version, replace, or fork before shipping. Each advisory is listed with its OSV/GHSA identifier below.

The safest reading is to replace, fork, or tightly pin event-stream and stop taking on new exposure to it. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.