JSPM

@cyberhub/trust-node-openssl

1.0.1
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 12
  • Score
    100M100P100Q68155F
  • License MIT

Security Trust Report: node-openssl@0.0.2-security — 63/100 (C+, standard). 1 vulnerability found. Maintainer risk, supply chain analysis from 8 security databases.

Package Exports

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@cyberhub/trust-node-openssl) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    Security Trust Report: node-openssl

    node-openssl@0.0.2-security: 63/100 | Grade: C+ | Tier: STANDARD (confidence: ±3)

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

    TL;DR

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

    Score Breakdown

    Maintainer Trust:  █████████░░░░░░░░░░░ 43/100
Package Health:    ████████████████░░░░ 80/100
Supply Chain:      █████████████████░░░ 83/100
Community:         ██████████░░░░░░░░░░ 48/100

    Why this score?

    • Maintainer Trust is 43 because: single maintainer (bus factor risk), maintainer changes detected
    • Community is 48 because: GitHub repo inactive

    Vulnerabilities (1 vulnerability)

    Severity Count
    🟠 High 1
    ⚪ Low 1

    Key Risk Flags

    • 🟠 HIGH: Primary maintainer account is less than 6 months old (0 days)
    • 🟠 HIGH: Maintainer(s) removed in v1.0.2: hacktask (evidence)
    • 🟠 HIGH: Maintainer(s) removed in v0.0.2-security: npm-support (evidence)
    • 🟠 HIGH: No license declared
    • 🟠 HIGH: 1 HIGH vulnerability detected

    🛠️ What Should You Do?

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

    Maintainers (1)

    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 node-openssl — 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 node-openssl team. Updated 2026-04-13.