@cyberhub/trust-find-root
v1.0.0
Published
Security Trust Report: [email protected] — 64/100 (C+, standard). Maintainer risk, supply chain analysis from 8 security databases.
Downloads
24
Maintainers
Readme
Security Trust Report: find-root
[email protected]: 64/100 | Grade: C+ | Tier: STANDARD (confidence: ±3)
Scanned on 2026-04-09 from 8 security databases. View package on npm →
TL;DR
- No maintainers listed
- Pin your version and monitor for changes
Score Breakdown
Maintainer Trust: ██████░░░░░░░░░░░░░░ 30/100
Package Health: ██████████████████░░ 88/100
Supply Chain: ████████████████████ 98/100
Community: ██████████░░░░░░░░░░ 48/100Why this score?
- Maintainer Trust is 30 because: single maintainer (bus factor risk), no 2FA on published versions, maintainer changes detected
- Community is 48 because: GitHub repo inactive
Vulnerabilities
✅ No known vulnerabilities detected across 8 security databases.
Key Risk Flags
- 🔴 CRITICAL: No maintainers listed
- 🔴 CRITICAL: No maintainers listed
- 🟠 HIGH: Maintainer(s) removed in v1.1.0: jden (evidence)
🛠️ What Should You Do?
Immediate:
Always: Pin version, run pkgtrust scan in CI, monitor at nrupak.com/trust/find-root
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 find-root — 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 find-root team. Updated 2026-04-09.
