Security Trust Report: @hoptrendy/hopcode-core

@hoptrendy/[email protected]: 65/100 | Grade: B | Tier: STANDARD (confidence: ±3)

Scanned on 2026-04-26 from 8 security databases. View package on npm →

TL;DR

• No critical vulnerabilities from live scan
• Pin your version and monitor for changes

Score Breakdown

Maintainer Trust:  ██████████████░░░░░░ 68/100
Package Health:    ██████████████░░░░░░ 68/100
Supply Chain:      ███████████░░░░░░░░░ 56/100
Community:         ██████████████░░░░░░ 70/100

Why this score?

• Supply Chain is 56 because: risky dependencies

Vulnerabilities

✅ No known vulnerabilities detected across 8 security databases.

Key Risk Flags

• 🟠 HIGH: Primary maintainer account is less than 6 months old (7 days)
• 🟠 HIGH: Burst publishing detected — 5+ versions in a single day
• 🟠 HIGH: 81 direct dependencies — large attack surface
• 🟠 HIGH: No license declared
• 🟠 HIGH: Depends on historically compromised package: tar

🛠️ What Should You Do?

Always: Pin version, run pkgtrust scan in CI, monitor at nrupak.com/trust/@hoptrendy/hopcode-core

Maintainers (1)

• taimoor214 ✅ 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 @hoptrendy/hopcode-core — 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 @hoptrendy/hopcode-core team. Updated 2026-04-26.