Security Trust Report: @xmorse/playwright-core

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

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

TL;DR

• Depends on breached package "colors"
• Pin your version and monitor for changes

Score Breakdown

Maintainer Trust:  █████████████░░░░░░░ 66/100
Package Health:    █████████████████░░░ 84/100
Supply Chain:      █████████░░░░░░░░░░░ 43/100
Community:         █████████████░░░░░░░ 66/100

Why this score?

• Supply Chain is 43 because: risky dependencies

Vulnerabilities

✅ No known vulnerabilities detected across 8 security databases.

Key Risk Flags

• 🔴 CRITICAL: Depends on breached package "colors"
• 🟠 HIGH: Primary maintainer account is less than 6 months old (82 days)
• 🟠 HIGH: Depends on historically compromised package: colors
• 🟠 HIGH: Depends on historically compromised package: minimatch
• 🟠 HIGH: 2 direct dependencies have known security issues

🛠️ What Should You Do?

Immediate:

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

Maintainers (1)

• xmorse ✅ 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 @xmorse/playwright-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 @xmorse/playwright-core team. Updated 2026-04-29.