io.github.pixell-global/sayou

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

  fail25% of grade

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

  Python build script executes at build time: network call in build script

• 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. benchmarks/runner/judge.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: sayou/__main__.py: references a sensitive credential path (/mcp.json) — the tool-poisoning exfiltration target. HIGH: shell/exec capability AND network egress together — download-and-execute risk (agent/sandbox/manager.py: subprocess.* call with shell=True (command-injection prone); agent/benchmarks/eval.py: outbound HTTP/socket call). HIGH: shell/exec capability AND destructive filesystem writes together (agent/sandbox/manager.py: subprocess.* call with shell=True (command-injection prone); benchmarks/generate.py: open(…, 'w'/'a'/'x') write-mode file access). discloses shell/exec capability: agent/sandbox/manager.py: subprocess.* call with shell=True (command-injection prone) discloses shell/exec capability: scripts/helpers.js: imports child_process and calls exec/spawn discloses dynamic code execution: tests/test_rest_api.py: uses eval/exec/__import__ discloses broad/destructive filesystem access: benchmarks/generate.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: benchmarks/runner/report.py: open(…, 'w'/'a'/'x') write-mode file access discloses broad/destructive filesystem access: benchmarks/runner/adapters/sayou_adapter.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: examples/ask.py: recursive glob ('**') from a broad root discloses broad/destructive filesystem access: examples/file_operations.py: recursive glob ('**') from a broad root discloses broad/destructive filesystem access: examples/research_agent.py: recursive glob ('**') from a broad root discloses broad/destructive filesystem access: sayou/cli/init.py: open(…, 'w'/'a'/'x') write-mode 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.pixell-global/[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

  warn10% of grade

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

  manifest/source references tracking behavior — disclosure