Security Trust Report: @seafile/sdoc-editor

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

Scanned on 2026-04-21 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:  ███████████████░░░░░ 77/100
Package Health:    ████████████████░░░░ 81/100
Supply Chain:      █████████░░░░░░░░░░░ 43/100
Community:         ████████░░░░░░░░░░░░ 40/100

Why this score?

• Supply Chain is 43 because: 1 known CVEs, risky dependencies
• Community is 40 because: no public GitHub repo linked (may be private or on another platform)

Vulnerabilities (1 vulnerability)

| Severity | Count | |----------|-------| | 🟡 Medium | 1 |

• CVE-2026-30587
• GHSA-rqj3-x344-qvxc

Key Risk Flags

• 🟠 HIGH: Maintainer(s) removed in v0.5.77: seafile (evidence)
• 🟠 HIGH: Burst publishing detected — 5+ versions in a single day
• 🟠 HIGH: Depends on historically compromised package: axios
• 🟠 HIGH: 1 direct dependencies have known security issues

🛠️ What Should You Do?

Always: Pin version, run pkgtrust scan in CI, monitor at nrupak.com/trust/@seafile/sdoc-editor

Maintainers (1)

• seafile ✅ 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 @seafile/sdoc-editor — 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 @seafile/sdoc-editor team. Updated 2026-04-21.