Security Trust Report: @databricks/sql

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

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

TL;DR

• No maintainers listed
• Pin your version and monitor for changes

Score Breakdown

Maintainer Trust:  ██████░░░░░░░░░░░░░░ 28/100
Package Health:    ██████████████████░░ 89/100
Supply Chain:      ██████████████░░░░░░ 71/100
Community:         █████████████░░░░░░░ 67/100

Why this score?

• Maintainer Trust is 28 because: single maintainer (bus factor risk), no 2FA on published versions, maintainer changes detected

Vulnerabilities

✅ No known vulnerabilities detected across 8 security databases.

Key Risk Flags

• 🔴 CRITICAL: No maintainers listed
• 🔴 CRITICAL: No maintainers listed
• 🔴 CRITICAL: Package name "@databricks/sql" is 2 edit(s) from popular "mysql"
• 🟠 HIGH: Maintainer(s) removed in v1.9.0: arikfr (evidence)
• 🟠 HIGH: Maintainer(s) removed in v1.11.0: gcpantazis (evidence)

🛠️ What Should You Do?

Immediate:

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

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 @databricks/sql — 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 @databricks/sql team. Updated 2026-05-02.