Security Trust Report: @evocrawl/js

@evocrawl/js@: 51/100 | Grade: C | Tier: STANDARD (confidence: ±3)

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

TL;DR

• No maintainers listed
• Pin your version and monitor for changes

Score Breakdown

Maintainer Trust:  ███████░░░░░░░░░░░░░ 36/100
Package Health:    ███████████████░░░░░ 73/100
Supply Chain:      ███████████░░░░░░░░░ 56/100
Community:         ████████░░░░░░░░░░░░ 40/100

Why this score?

• Maintainer Trust is 36 because: single maintainer (bus factor risk), no 2FA on published versions
• Supply Chain is 56 because: limited supply chain data
• 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: No maintainers listed
• 🔴 CRITICAL: No maintainers listed
• 🔴 CRITICAL: Package name "@evocrawl/js" is 2 edit(s) from popular "jest"
• 🟠 HIGH: No license declared

🛠️ What Should You Do?

Immediate:

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

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 @evocrawl/js — 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 @evocrawl/js team. Updated 2026-04-24.