vmware-monitor@2.6.0
VERIFIED· install onlyPublisher claims: "Use for read-only VMware/vSphere/ESXi inventory, health, alarms, events and VM/host/datastore investigations; cross-cluster or cross-vCenter triage such as "is anything on fire", "what needs attention now" and "what is happening around this VM". No tool changes a VMware resource. Local config, audit, HTML snapshots and an explicitly started daemon write local state; optional webhooks send disclosed operational data to configured URLs. For VM writes use vmware-aiops, NSX networking vmware-nsx, metrics/capacity vmware-aria, and AVI/AKO vmware-avi." 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
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-08 and scored it 83/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
…rites** (this machine only): `init` writes `~/.vmware-monitor/config.yaml` and `.env` (0600; plaintext passwords are rewritten as `b64:` on load); audit logs `~/.vm…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…vCenter/ESXi target requires a per-target password env var in ~/.vmware-monitor/.env following the pattern VMWARE_<TARGET_NAME_UPPER>_PASSWORD (e.g., target "vcente…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.vmware-monitor init # guided: prompts for host/user/password, writes config + .env (chmod 600), then verifiesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.locks `.env` to 0600. Prefer it over hand-editing; manual steps:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.vmware-monitor init # guided: prompts for host/user/password, writes config + .env (chmod 600), then verifiesFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.…laintext passwords are rewritten as `b64:` on load); audit logs `~/.vmware/audit.db` (MCP and CLI) and `~/.vmware-monitor/audit.log` (CLI); `--html` snapshots in `~/vmware-health/`; after `daemon start` only, `scan.log`, `daemon.pid` and o…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.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.