Security Trust Report: react-dom.js

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

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

TL;DR

• 1 vulnerability found (0 critical, 0 high)
• Pin your version and monitor for changes

Score Breakdown

Maintainer Trust:  ████████░░░░░░░░░░░░ 41/100
Package Health:    ████████████████░░░░ 80/100
Supply Chain:      ██████████████████░░ 90/100
Community:         █████████░░░░░░░░░░░ 47/100

Why this score?

• Maintainer Trust is 41 because: single maintainer (bus factor risk), no 2FA on published versions
• Community is 47 because: GitHub repo inactive

Vulnerabilities (1 vulnerability)

| Severity | Count | |----------|-------| | ⚪ Low | 1 |

• MAL-2025-31780

Key Risk Flags

• 🔴 CRITICAL: No maintainers listed
• 🔴 CRITICAL: No maintainers listed
• 🟠 HIGH: No license declared

🛠️ What Should You Do?

Immediate:

• Upgrade to the latest version (npm update react-dom.js)

Always: Pin version, run pkgtrust scan in CI, monitor at nrupak.com/trust/react-dom.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 react-dom.js — 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 react-dom.js team. Updated 2026-04-06.