MCP server · trust report

io.github.zw008/vmware-log-insight

1 check that ran failed — version behavior — so this release can’t be trusted as-is.

Publisher
io.github.zw008
Repository
github.com/zw008/VMware-Log-Insight
Install
pypi:vmware-log-insight, pypi:vmware-log-insight, pypi:vmware-log-insight, pypi:vmware-log-insight, pypi:vmware-log-insight, pypi:vmware-log-insight, pypi:vmware-log-insight
Versions
7
Inspected
5 of 6 checks · 75%
Scored
2026-07-20 · rubric 1.0.0

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.

6 checks2 clean3 flagged1 not inspected
  • 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/eval/capability/conftest.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

    warn15% of grade

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

    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_log_insight/config.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

Version history

Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.

VersionPublishedGradeScoreInspectedChange
v1.8.5 · current2026-07-20 B77.55/6 · 75%C→B in v1.8.5
v1.8.42026-07-20 C67.53/6 · 55%B→C in v1.8.4
v1.8.12026-07-19 B754/6 · 65%±0
v1.8.02026-07-19 B754/6 · 65%±0
v1.6.12026-06-24 B753/6 · 55%