io.github.zw008/vmware-monitor

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

• Injection surface

  unscannable25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.

• Supply chain

  pass25% of grade

  Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

  repository linkage verified

• Credential hygiene

  pass15% of grade

  How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

  Reads secrets from the environment (e.g. tests/test_config.py) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• Permission scope

  fail15% of grade

  Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

  HIGH: shell/exec capability AND network egress together — download-and-execute risk (tests/test_no_destructive_code.py: subprocess.* call; vmware_monitor/notify/webhook.py: outbound HTTP/socket call). HIGH: shell/exec capability AND destructive filesystem writes together (tests/test_no_destructive_code.py: subprocess.* call; tests/eval/regression/test_env_secret_obfuscation.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: tests/test_no_destructive_code.py: subprocess.* call discloses broad/destructive filesystem access: tests/eval/regression/test_env_secret_obfuscation.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: vmware_monitor/config.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: vmware_monitor/init_wizard.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: vmware_monitor/notify/audit.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: vmware_monitor/notify/audit.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: vmware_monitor/notify/logger.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: vmware_monitor/scanner/scheduler.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

• Version behavior

  fail10% of grade

  Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

  vs prior 1.8.4 (patch bump): new hardcoded outbound host/BCC destination(s): admin.

• Transport config

  warn10% of grade

  Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

  manifest/source references analytics behavior — disclosure