JSPM

@cyberhub/trust-symbioticsec-code

1.0.4
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 39
  • Score
    100M100P100Q90104F
  • License MIT

Security Trust Report: @symbioticsec/code@0.3.1 — 63/100 (C+, standard). 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-symbioticsec-code) 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: @symbioticsec/code

    @symbioticsec/code@0.3.1: 63/100 | Grade: C+ | Tier: STANDARD (confidence: ±3)

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

    TL;DR

    • Package name "@symbioticsec/code" is 2 edit(s) from popular "cors"
    • Pin your version and monitor for changes

    Score Breakdown

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

    Why this score?

    • Supply Chain is 56 because: limited supply chain data
    • Community is 40 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 "@symbioticsec/code" is 2 edit(s) from popular "cors"
    • 🟠 HIGH: Primary maintainer account is less than 6 months old (18 days)
    • 🟠 HIGH: Burst publishing detected — 5+ versions in a single day

    🛠️ What Should You Do?

    Immediate:

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

    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 @symbioticsec/code — 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 @symbioticsec/code team. Updated 2026-04-27.