vmware-privateai@2.5.3
VERIFIED· install onlyPublisher claims: "Use for VMware Private AI Foundation with NVIDIA on vSphere 9.x/VCF 9.1: GPU inventory/readiness/utilization, vGPU consumers and profiles, DirectPath catalog, vGPU assignment, and PAIS served models, knowledge bases, catalogs/data sources and MCP gallery. Trigger on "list GPU hosts", "which VMs use a vGPU", "GPU utilization", "assign a vGPU profile" or "list served models" in VMware/NVIDIA context. Supporting commands check access, estimate model sizing locally and inspect local air-gap bundles without contacting a model provider. For backing VM power/snapshot/clone/migrate use vmware-aiops, general health/alarms vmware-monitor, or GPU-enabled Tanzu Kubernetes vmware-vks." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What changed since 2.5.2
vet-skills diff vmware-privateai 2.5.2 2.5.3In the sandbox, this version reached for nothing 2.5.2 did not. Compared from the two recorded runs, not from source.
2.5.2 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 ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-11 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
the PAIS bearer token live in `~/.vmware-privateai/.env` (chmod 600). See `references/setup-guide.md`.Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.add that line to `~/.vmware-privateai/.env` and `chmod 600` it, or export it (from a secret manager).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.only; passwords and the PAIS bearer token live in `~/.vmware-privateai/.env` (0600, obfuscated toFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.the PAIS bearer token live in `~/.vmware-privateai/.env` (chmod 600). See `references/setup-guide.md`.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.add that line to `~/.vmware-privateai/.env` and `chmod 600` it, or export it (from a secret manager).Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.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.