Security Trust Report: jst

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

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

TL;DR

• Package name "jst" is 1 edit(s) from popular "jest"
• Pin your version and monitor for changes

Score Breakdown

Maintainer Trust:  ███████████░░░░░░░░░ 56/100
Package Health:    ████████████████░░░░ 78/100
Supply Chain:      ███████████░░░░░░░░░ 56/100
Community:         ████████░░░░░░░░░░░░ 42/100

Why this score?

• Maintainer Trust is 56 because: single maintainer (bus factor risk)
• Supply Chain is 56 because: limited supply chain data
• Community is 42 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: Package name "jst" is 1 edit(s) from popular "jest"
• 🟠 HIGH: Primary maintainer account is less than 6 months old (0 days)
• 🟠 HIGH: No license declared

🛠️ What Should You Do?

Immediate:

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

Maintainers (1)

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