@cyberhub/trust-event-stream
v1.0.62
Published
Security Trust Report: [email protected] — 54/100 (C, standard). Security incident detected. Maintainer risk, supply chain analysis from 8 security databases.
Maintainers
Readme
Security Trust Report: event-stream
[email protected]: 54/100 | Grade: C | Tier: STANDARD (confidence: ±3)
Data verified on 2026-04-02 from 8 security databases.
TL;DR
- Security incident detected — compromised via account takeover/sabotage
- Consider switching to highland (High-level streams library)
- Pin your version and monitor for changes
⚠️ Security Incident Background
In November 2018, a malicious contributor (@right9ctrl) gained maintainer access through social engineering and injected a cryptocurrency-stealing payload via the flatmap-stream dependency. The attack targeted Copay Bitcoin wallets and affected 2M+ downstream projects.
Score Breakdown
Maintainer Trust: █████████░░░░░░░░░░░ 44/100
Package Health: █████████████████░░░ 86/100
Supply Chain: ████████░░░░░░░░░░░░ 39/100
Community: █████████░░░░░░░░░░░ 46/100Why this score?
- Maintainer Trust is 44 because: single maintainer (bus factor risk), maintainer changes detected
- Supply Chain is 39 because: 1 security incident(s) in breach database, in breach database
- Community is 46 because: no public GitHub repo linked (may be private or on another platform)
⚠️ Security Incident
This package was compromised via account takeover/sabotage (no CVE assigned). See Security Incident Background above for details.
Key Risk Flags
- 🔴 CRITICAL: HISTORICAL BREACH: Malicious code injected via flatmap-stream (2018)
- 🔴 CRITICAL: 1 CRITICAL security incident from breach database (no CVE assigned)
- 🟠 HIGH: Primary maintainer account is less than 6 months old (0 days)
- 🟠 HIGH: Maintainer(s) removed in v4.0.0: dominictarr
- 🟠 HIGH: Burst publishing detected — 5+ versions in a single day
🛠️ What Should You Do?
Immediate:
- 📌 Pin to known-safe version: 3.3.4 (before flatmap-stream injection)
- 🔄 Or replace with highland — High-level streams library
- 📖 Review the security incident above
Always: Pin version, run pkgtrust scan in CI, monitor at nrupak.com/trust/event-stream
🔄 Safer Alternatives
| Package | Why | Trust Report | |---------|-----|-------------| | highland | High-level streams library | View score | | Node.js streams | Built-in, no dependency needed | View score | | through2 | Simple stream wrapper | View score |
Maintainers
- npm ✅ 2FA (org)
Methodology: 18+ signals across 4 categories (Maintainer 35%, Package 25%, Supply Chain 25%, Community 15%). Full scoring docs →
Check your project: npm i -g @cyberhub/pkgtrust && pkgtrust scan event-stream — CLI docs
Data Sources: GitHub Advisories · OSV.dev · npm audit · Snyk · Socket.dev · npms.io · Bundlephobia · deps.dev
Report by pkgtrust · Dashboard · Compare · CLI
This is an automated security report. Not affiliated with the event-stream team. Updated 2026-04-02.
