Security Trust Report: wepback

[email protected]: 60/100 | Grade: C+ | Tier: STANDARD (confidence: ±3)

Scanned on 2026-05-18 from 8 security databases. View package on npm →

TL;DR

• Package is deprecated: Package abandoned, contact [email protected] for more inf
• Pin your version and monitor for changes

Score Breakdown

Maintainer Trust:  ██████████░░░░░░░░░░ 49/100
Package Health:    ███████████████░░░░░ 74/100
Supply Chain:      ██████████████░░░░░░ 71/100
Community:         ████████░░░░░░░░░░░░ 41/100

Why this score?

• Maintainer Trust is 49 because: single maintainer (bus factor risk), maintainer changes detected
• Community is 41 because: GitHub repo inactive

Vulnerabilities

✅ No known vulnerabilities detected across 8 security databases.

Key Risk Flags

• 🔴 CRITICAL: Package is deprecated: Package abandoned, contact [email protected] for more info.
• 🔴 CRITICAL: Package name "wepback" is 2 edit(s) from popular "webpack"
• 🟠 HIGH: Primary maintainer account is less than 6 months old (0 days)
• 🟠 HIGH: Maintainer(s) removed in v1.0.0: hagb4rd (evidence)

🛠️ What Should You Do?

Immediate:

Always: Pin version, run pkgtrust scan in CI, monitor at nrupak.com/trust/wepback

Maintainers (1)

• npm ✅ 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 wepback — 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 wepback team. Updated 2026-05-18.