vmware-nsx@1.15.4
CAUTION· static onlyPublisher claims: "Use for VMware NSX/NSX-T networking: segments, Tier-0/Tier-1 gateways, NAT, BGP, static routes, IP pools, fabric inventory, health and connectivity diagnostics. Trigger on "create segment", "configure gateway", "add NAT rule", "check NSX health" or NSX network troubleshooting. Supporting commands configure the local MCP client; default stdio is local, and opt-in authenticated HTTPS opens a listener. For DFW/security groups use vmware-nsx-security, vSphere port groups/VMkernel adapters or VM lifecycle vmware-aiops, AVI/ALB vmware-avi, and multi-step workflows vmware-pilot. Do not use for networking outside NSX." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
What changed since 1.15.2
vet-skills diff vmware-nsx 1.15.2 1.15.4In the sandbox, this version reached for nothing 1.15.2 did not. Compared from the two recorded runs, not from source.
1.15.4 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-19 and scored it 58/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Collapsed <details> block carrying instructions. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
vmware-nsx init # guided setup: writes config + .env (chmod 600, password grep-safe), then verifiesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.vmware-nsx init # writes ~/.vmware-nsx/config.yaml + .env (chmod 600), then verifiesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary>Preinstalled CLI and additional MCP options</summary> ### MCP Server **After `uv tool install vmware-nsx-mgmt==1.15.4`, start the MCP server with one cFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- **Credential safety**: Passwords loaded only from environment variables (`.env` file), never from `config.yaml`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.vmware-nsx init # guided setup: writes config + .env (chmod 600, password grep-safe), then verifiesFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.vmware-nsx init # writes ~/.vmware-nsx/config.yaml + .env (chmod 600), then verifiesFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.…rget `nsx-prod` needs `VMWARE_NSX_NSX_PROD_PASSWORD`. Check your `~/.vmware-nsx/.env` file. ## Safety - **Read-heavy**: 20 of 33 tools are read-only (list, get, s…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…Each NSX Manager target requires a per-target password env var in ~/.vmware-nsx/.env following the pattern VMWARE_NSX_<TARGET_NAME_UPPER>_PASSWORD. Username/passwor…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
22 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim zw008: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.