Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.SAP/mdk-mcp-server

NPM · @SAP/MDK-MCP-SERVER · SCANNED AUG 10

Model Context Protocol (MCP) server for AI-assisted development of MDK applications.

Available components

npm · @sap/mdk-mcp-server 0
−30 this week 0 Trust /100

Recent critical change

CVE-2026-25896 affects this package (7 Aug 2026). See the changelog before you install this server.

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security67
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 400 of 1073 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. View diagnostics → Unverified
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 12 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package declared that it provides tools, but our sandbox run could not list them, so the captured schema is incomplete.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package declared that it provides tools, but our sandbox run could not list them.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 3 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @sap/mdk-mcp-server

# add to Claude Code
claude mcp add sap-mdk-mcp-server -- npx -y @sap/mdk-mcp-server
# add to Codex CLI
codex mcp add sap-mdk-mcp-server -- npx -y @sap/mdk-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sap-mdk-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@sap/mdk-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sap-mdk-mcp-server --command npx --arg -y --arg @sap/mdk-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  sap-mdk-mcp-server:
    command: "npx"
    args: ["-y", "@sap/mdk-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "sap-mdk-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@sap/mdk-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 7 Aug 26 −31
    • CVE-2026-25896 affects this package: high ▼ critical
    • CVE-2025-7783 affects this package: high ▼ critical
    • Score status: scored → failed ▼ critical
    • Known CVEs: CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. critical
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: Tool coverage not yet verified: this package declared that it provides tools, but our sandbox run could not list them. functional
    • Schema quality: Schema quality not yet verified: this package declared that it provides tools, but our sandbox run could not list them, so the captured schema is incomplete. functional
  • 6 Aug 26 0
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2023-28155 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-45736 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2021-23337 affects this package: high ▼ security
    • CVE-2026-48779 affects this package: high ▼ security
    • CVE-2026-33532 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-39244 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2022-33987 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-42089 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2025-13465 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • GHSA-f88m-g3jw-g9cj affects this package: high ▼ security
  • 5 Aug 26 0
    • GHSA-f88m-g3jw-g9cj affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-45736 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2021-23337 affects this package: high ▼ security
    • CVE-2026-48779 affects this package: high ▼ security
    • CVE-2026-33532 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2023-28155 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-39244 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2022-33987 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-42089 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2025-13465 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
  • 4 Aug 26 +1
    • CVE-2026-67316 affects this package: high ▼ security
    • GHSA-f88m-g3jw-g9cj affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2025-13465 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-42089 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2022-33987 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-39244 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2023-28155 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2026-33532 affects this package: high ▼ security
    • CVE-2026-48779 affects this package: high ▼ security
    • CVE-2021-23337 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-45736 affects this package: high ▼ security
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
  • 3 Aug 26 −1
    • GHSA-f88m-g3jw-g9cj affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-45736 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2021-23337 affects this package: high ▼ security
    • CVE-2026-48779 affects this package: high ▼ security
    • CVE-2026-33532 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2023-28155 affects this package: high ▼ security
    • CVE-2026-67317 affects this package: high ▼ security
    • CVE-2026-42035 affects this package: high ▼ security
    • CVE-2026-44486 affects this package: high ▼ security
    • CVE-2026-42036 affects this package: high ▼ security
    • CVE-2026-39244 affects this package: high ▼ security
    • CVE-2026-42033 affects this package: high ▼ security
    • CVE-2026-42038 affects this package: high ▼ security
    • CVE-2026-67319 affects this package: high ▼ security
    • CVE-2026-67313 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2026-42034 affects this package: high ▼ security
    • CVE-2026-44494 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2022-33987 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-42089 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2025-13465 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
  • 2 Aug 26 +25

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2026-44496 affects this package: high ▼ security
    • CVE-2026-42043 affects this package: high ▼ security
    • CVE-2026-42040 affects this package: high ▼ security
    • GHSA-f88m-g3jw-g9cj affects this package: high ▼ security
    • CVE-2026-44490 affects this package: high ▼ security
    • CVE-2026-44487 affects this package: high ▼ security
    • CVE-2026-45736 affects this package: high ▼ security
    • CVE-2025-62718 affects this package: high ▼ security
    • CVE-2026-44495 affects this package: high ▼ security
    • CVE-2021-23337 affects this package: high ▼ security
    • CVE-2026-48779 affects this package: high ▼ security
    • CVE-2026-33532 affects this package: high ▼ security
    • CVE-2026-42264 affects this package: high ▼ security
    • CVE-2023-28155 affects this package: high ▼ security
    • CVE-2026-42044 affects this package: high ▼ security
    • CVE-2026-42041 affects this package: high ▼ security
    • CVE-2026-40175 affects this package: high ▼ security
    • CVE-2022-33987 affects this package: high ▼ security
    • CVE-2026-67316 affects this package: high ▼ security
    • CVE-2026-42039 affects this package: high ▼ security
    • CVE-2026-44488 affects this package: high ▼ security
    • CVE-2026-25639 affects this package: high ▼ security
    • CVE-2026-42089 affects this package: high ▼ security
    • CVE-2026-67312 affects this package: high ▼ security
    • CVE-2026-42042 affects this package: high ▼ security
    • CVE-2026-42037 affects this package: high ▼ security
    • Known CVEs: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Provenance: Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. security
    • Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
    • Maintenance: unverified → pass ▲ functional
    • License: unverified → pass ▲ functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Licence: Apache-2.0 functional
  • 1 Aug 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 31 Jul 26 −1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 10 Aug 2026 · Analysed npm/@sap/[email protected]

Provenance Repository mismatch

The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale.

Result Repository mismatch
Ecosystem npm
Reason Repository mismatch
Discovered via Registry attestation endpoint
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/SAP/mdk-mcp-server/.github/workflows/npm-publish.yml@refs/heads/rel-0.3.0
Rekor log index 1340513866
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:d68eea59c334cd034c680929b50b24bb0040fce6d72dfdc0eab458ce3bd0cdad89aeaacde6e60d51e080c2433fdf1da55d7a5efcf11ea2e07cb3fb2cf
Vulnerabilities 57 findings
ID CVE Severity Vector Fix available
GHSA-8988-4f7v-96qf CVE-2026-54285 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-xcpc-8h2w-3j85 CVE-2026-39244 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-2g4f-4pwh-qvx6 CVE-2025-69873 medium yes
GHSA-35jp-ww65-95wh CVE-2026-44494 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N yes
GHSA-3g43-6gmg-66jw CVE-2026-44495 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-3p68-rc4w-qgx5 CVE-2025-62718 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-3w6x-2g7m-8v23 CVE-2026-42044 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N yes
GHSA-42h9-826w-cgv3 CVE-2026-67313 medium yes
GHSA-43fc-jf86-j433 CVE-2026-25639 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-445q-vr5w-6q77 CVE-2026-42037 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-5c9x-8gcm-mpgx CVE-2026-42034 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-62hf-57xw-28j9 CVE-2026-42039 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6chq-wfr3-2hj9 CVE-2026-42035 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-777c-7fjr-54vf CVE-2026-44488 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-7q8q-rj6j-mhjq CVE-2026-67319 medium yes
GHSA-898c-q2cr-xwhg CVE-2026-44490 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-fvcv-3m26-pcqx CVE-2026-40175 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-hfxv-24rg-xrqf CVE-2026-44496 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-j5f8-grm9-p9fc CVE-2026-44486 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-jqh4-m9w3-8hp9 CVE-2026-67317 medium yes
GHSA-m7pr-hjqh-92cm CVE-2026-42038 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N yes
GHSA-mmx7-hfxf-jppx CVE-2026-67316 medium yes
GHSA-p92q-9vqr-4j8v CVE-2026-44487 high yes
GHSA-pf86-5x62-jrwf CVE-2026-42033 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-pmv8-rq9r-6j72 CVE-2026-67312 medium yes
GHSA-pmwg-cvhr-8vh7 CVE-2026-42043 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-q8qp-cvcw-x6jj CVE-2026-42264 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-vf2m-468p-8v99 CVE-2026-42036 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-w9j2-pvgh-6h63 CVE-2026-42041 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-xhjh-pmcv-23jw CVE-2026-42040 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-xx6v-rp6x-q39c CVE-2026-42042 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-8gc5-j5rx-235r CVE-2026-33036 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-fj3w-jwp8-x2g3 CVE-2026-27942 low yes
GHSA-gh4j-gqv2-49f6 CVE-2026-41650 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-jmr7-xgp7-cmfj CVE-2026-26278 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-jp2q-39xq-3w4g CVE-2026-33349 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-m7jm-9gc2-mpf2 CVE-2026-25896 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N yes
GHSA-fjxv-7rqg-78g4 CVE-2025-7783 critical yes
GHSA-hmw2-7cc7-3qxx CVE-2026-12143 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-pfrx-2q88-qq97 CVE-2022-33987 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-5p2g-fcmc-qvqq CVE-2025-71329 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
GHSA-w3rx-r6r6-pgpr CVE-2025-71330 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
GHSA-52cp-r559-cp3m CVE-2026-59869 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-5p4m-2wfm-xmqj high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-h67p-54hq-rp68 CVE-2026-53550 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-f23m-r3pf-42rh CVE-2025-13465 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-r5fr-rjxr-66jc CVE-2021-23337 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-xxjr-mmjv-4gpg CVE-2025-13465 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-6rw7-vpxm-498p CVE-2025-15284 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-p8p7-x288-28g6 CVE-2023-28155 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes

Showing 50 of 57 vulnerabilities.

Dependencies 400 packages
Packages resolved 400
Deprecated 4
Stale 102
No linked repository 2
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

The sandbox run completed and this package exposed no tools.