io.github.anulum/synapse-channel

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: subprocess 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. src/synapse_channel/agent_tmux.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.

  has both shell/exec and network egress — capable of download-and-run, though no such path was observed (src/synapse_channel/cli_cross_repo.py: subprocess.* call; src/synapse_channel/client/chat_backends.py: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (src/synapse_channel/cli_cross_repo.py: subprocess.* call; src/synapse_channel/core/archive_report.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: 11 files (src/synapse_channel/cli_cross_repo.py, src/synapse_channel/cli_doctor.py, src/synapse_channel/client/diagnostics.py, +8 more) discloses broad/destructive filesystem access: 7 files (src/synapse_channel/core/archive_report.py, src/synapse_channel/core/message_auth_durable.py, src/synapse_channel/core/persistence.py, +4 more) 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 0.99.22 (patch bump): new capability primitive(s) in source: child_process, fs-write, http-client, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, a2a-protocol.org, anulum.github.io, api.openai.com, example.test, github.com, host, ide.example, pypi.org, www.anulum.li, www.w3.org.

• 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 heartbeat behavior — disclosure