Case file No.452 · pypi · stdio

VMware Debug

io.github.vmware-skills/vmware-debug · v2.3.0

VMware incident timeline, root-cause routing, local case ledger; no vSphere access. 14 MCP tools.

Package ↗GitHub ↗

Security score

88/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 2 days ago

Source transparency10/15

public repo, license unknown/none

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

654 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v2.3.0)Oct 17, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is VMware Debug safe?

MCPWatch gives VMware Debug a heuristic security score of 88/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does VMware Debug have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package vmware-debug. That is not proof of safety.

When was VMware Debug last updated?

The latest registry version is 2.3.0, published Oct 16, 2026. The last push to vmware-skills/VMware-Debug was on Oct 18, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does VMware Debug use?

GitHub did not detect a license for vmware-skills/VMware-Debug.

Related servers

same publisher / similar score