Security Trust Report: coa

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

Data verified on 2026-04-02 from 8 security databases.

TL;DR

• Security incident detected — compromised via account takeover/sabotage
• Pin your version and monitor for changes

⚠️ Security Incident Background

In November 2021, versions were published through a compromised maintainer account that included malicious code to steal credentials.

Score Breakdown

Maintainer Trust:  ████████████████░░░░ 79/100
Package Health:    █████████████████░░░ 87/100
Supply Chain:      ██░░░░░░░░░░░░░░░░░░ 12/100
Community:         █████████░░░░░░░░░░░ 46/100

Why this score?

• Supply Chain is 12 because: 1 security incident(s) in breach database, in breach database
• Community is 46 because: no public GitHub repo linked (may be private or on another platform)

⚠️ Security Incident

This package was compromised via account takeover/sabotage (no CVE assigned). See Security Incident Background above for details.

Key Risk Flags

• 🔴 CRITICAL: HISTORICAL BREACH: Malicious versions published via compromised maintainer (2021)
• 🔴 CRITICAL: 1 CRITICAL security incident from breach database (no CVE assigned)

🛠️ What Should You Do?

Immediate:

• 📌 Pin to known-safe version: 2.0.2 (before compromise)
• 📖 Review the security incident above

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

Maintainers

• qfox ✅ 2FA (freemail)
• veged ✅ 2FA (org)

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 coa — 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 coa team. Updated 2026-04-02.