@cyberhub/trust-dashcam
v1.0.0
Published
Security Trust Report: [email protected] — 55/100 (C+, standard). Maintainer risk, supply chain analysis from 8 security databases.
Downloads
51
Maintainers
Readme
Security Trust Report: dashcam
[email protected]: 55/100 | Grade: C+ | Tier: STANDARD (confidence: ±3)
Scanned on 2026-04-09 from 8 security databases. View package on npm →
TL;DR
- Depends on breached package "node-ipc"
- Pin your version and monitor for changes
Score Breakdown
Maintainer Trust: ███████████░░░░░░░░░ 54/100
Package Health: █████████████████░░░ 84/100
Supply Chain: ███████░░░░░░░░░░░░░ 36/100
Community: ████████░░░░░░░░░░░░ 40/100Why this score?
- Maintainer Trust is 54 because: single maintainer (bus factor risk)
- Supply Chain is 36 because: risky dependencies
- Community is 40 because: no public GitHub repo linked (may be private or on another platform)
Vulnerabilities
✅ No known vulnerabilities detected across 8 security databases.
Key Risk Flags
- 🔴 CRITICAL: Depends on breached package "node-ipc"
- 🟠 HIGH: Primary maintainer account is less than 6 months old (0 days)
- 🟠 HIGH: Burst publishing detected — 5+ versions in a single day
- 🟠 HIGH: Depends on historically compromised package: node-ipc
- 🟠 HIGH: 1 direct dependencies have known security issues
🛠️ What Should You Do?
Immediate:
Always: Pin version, run pkgtrust scan in CI, monitor at nrupak.com/trust/dashcam
Maintainers (1)
- ianj3nnings ✅ 2FA (org email) — Trust profile
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 dashcam — CLI docs
Data Sources: GitHub Advisories · OSV.dev · npm audit · Snyk · Socket.dev · npms.io · Bundlephobia · deps.dev · CISA KEV · Packagephobia · OpenSSF Scorecard · Ecosyste.ms · GitHub Enhanced · Keybase · npm Provenance
Report by pkgtrust · Dashboard · Compare · CLI
This is an automated security report. Not affiliated with the dashcam team. Updated 2026-04-09.
