Is flatmap-stream healthy, maintained, and safe?
No — flatmap-stream carries 2 unpatched critical advisories and should not be adopted without a remediation plan.
The verdict
OSPulse scores flatmap-stream at 0/100 (critical risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. No — flatmap-stream carries 2 unpatched critical advisories and should not be adopted without a remediation plan.
The last sign of life was 29 November 2018, more than 7 years ago (2797 days); by any practical measure the package looks abandoned. 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 3 known advisories for flatmap-stream, including 2 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 flatmap-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.
Evidence trail — deterministic, auditable
Known vulnerabilities (3)
- GHSA-9x64-5r7x-2q53 ↗CRITICAL
Malicious Package in flatmap-stream
- GHSA-mh6f-8j2x-4483 ↗CRITICAL
Critical severity vulnerability that affects event-stream and flatmap-stream
- MAL-2025-20690 ↗UNKNOWN
Malicious code in flatmap-stream (npm)
Key facts
- Latest version
- v0.0.1-security
- Last release
- 29 November 2018 (2797 days ago)
- Total releases
- 2
- First release
- 29 November 2018
- Package age
- 7.7 years
- Maintainers
- 1
- Known advisories
- 3
- Confidence
- High
Frequently asked
Is flatmap-stream still maintained?
It doesn't appear to be — the last release was 29 November 2018, over two years ago, which usually indicates an abandoned package.
Does flatmap-stream have known security vulnerabilities?
Yes — OSV lists 3 advisories for flatmap-stream, including 2 rated critical. See the advisory list on this page for the OSV/GHSA identifiers.
Is flatmap-stream safe to use?
No — flatmap-stream carries 2 unpatched critical advisories and should not be adopted without a remediation plan. OSPulse rates it 0/100 (critical risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
flatmap-stream is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-27 · scores are deterministic and recomputed on each refresh.