@cyberhub/trust-commondir
v1.0.8
Published
Security Trust Report: [email protected] — 65/100 (B, standard). Maintainer risk, supply chain analysis from 8 security databases.
Maintainers
Readme
Security Trust Report: commondir
[email protected]: 65/100 | Grade: B | Tier: STANDARD (confidence: ±3)
Scanned on 2026-04-03 from 8 security databases. View package on npm →
TL;DR
- Package name "commondir" is 2 edit(s) from popular "commander"
- Pin your version and monitor for changes
Score Breakdown
Maintainer Trust: ██████████░░░░░░░░░░ 51/100
Package Health: ██████████████████░░ 88/100
Supply Chain: ██████████████░░░░░░ 71/100
Community: ██████████░░░░░░░░░░ 48/100Why this score?
- Maintainer Trust is 51 because: single maintainer (bus factor risk)
- Community is 48 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: Package name "commondir" is 2 edit(s) from popular "commander"
- 🟠 HIGH: Primary maintainer account is less than 6 months old (0 days)
🛠️ What Should You Do?
Immediate:
Always: Pin version, run pkgtrust scan in CI, monitor at nrupak.com/trust/commondir
Maintainers (1)
- nopersonsmodules ✅ 2FA (freemail) — 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 commondir — 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 commondir team. Updated 2026-04-03.
