io.github.sparkvibe-io/GuardianShield

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.

  Python build script has no build-time network/exec; repository linkage verified

• Credential hygiene

  warn15% of grade

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

  tests/test_phase1a_ranges.py: embeds a PRIVATE KEY block. (in an example/sample file — lower severity, but a real key here still leaks.) tests/test_phase1a_ranges.py: assigns a literal to password (Supe…23 (len 14)) — non-provider secret literal; prefer environment intake. tests/test_secrets.py: embeds a PRIVATE KEY block. (in an example/sample file — lower severity, but a real key here still leaks.) tests/test_secrets.py: contains a hardcoded Google API key (AIza…45 (len 39)) — in an example/sample file; verify it is not a real key. tests/test_secrets.py: assigns a literal to password (Supe…s! (len 16)) — non-provider secret literal; prefer environment intake. tests/test_secrets.py: assigns a literal to api_key (sk-a…HI (len 21)) — non-provider secret literal; prefer environment intake. tests/test_secrets.py: assigns a literal to password (MyP@…23 (len 14)) — non-provider secret literal; prefer environment intake. tests/test_secrets.py: assigns a literal to password (Sup3…e! (len 12)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. src/guardianshield/mcp_server.py) — the recommended intake shape.

• 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 (src/guardianshield/patterns/python.py: subprocess.* call with shell=True (command-injection prone); src/guardianshield/osv.py: outbound HTTP/socket call). HIGH: shell/exec capability AND destructive filesystem writes together (src/guardianshield/patterns/python.py: subprocess.* call with shell=True (command-injection prone); tests/test_manifest.py: path traversal ('../') combined with file access). discloses shell/exec capability: src/guardianshield/patterns/python.py: subprocess.* call with shell=True (command-injection prone) discloses shell/exec capability: src/guardianshield/patterns/python.py: os.system/os.popen/os.exec* call discloses shell/exec capability: tests/test_core.py: os.system/os.popen/os.exec* call discloses shell/exec capability: tests/test_patterns.py: subprocess.* call with shell=True (command-injection prone) discloses shell/exec capability: tests/test_patterns.py: os.system/os.popen/os.exec* call discloses shell/exec capability: tests/test_phase1a_ranges.py: os.system/os.popen/os.exec* call discloses shell/exec capability: tests/test_remediation.py: os.system/os.popen/os.exec* call discloses shell/exec capability: tests/test_scanner.py: subprocess.* call with shell=True (command-injection prone) discloses shell/exec capability: tests/test_scanner.py: os.system/os.popen/os.exec* call discloses dynamic code execution: src/guardianshield/patterns/common.py: uses eval/exec/__import__ discloses dynamic code execution: src/guardianshield/patterns/javascript.py: uses eval/exec/__import__ discloses dynamic code execution: src/guardianshield/patterns/python.py: uses eval/exec/__import__ discloses dynamic code execution: tests/test_mcp_server.py: uses eval/exec/__import__ discloses dynamic code execution: tests/test_patterns.py: uses eval/exec/__import__ discloses dynamic code execution: tests/test_phase1a_ranges.py: uses eval/exec/__import__ discloses dynamic code execution: tests/test_remediation.py: uses eval/exec/__import__ discloses dynamic code execution: tests/test_scanner.py: uses eval/exec/__import__ discloses broad/destructive filesystem access: tests/test_manifest.py: path traversal ('../') combined with file access Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

• Version behavior

  unscannable10% of grade

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

  no prior version to diff (first sight of io.github.sparkvibe-io/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.

• Transport config

  unscannable10% of grade

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

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.