io.github.phasespace-labs/palinode

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

  warn15% of grade

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

  tests/test_consolidation_run_lock.py: assigns a literal to token (repl…er (len 17)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. palinode/api/rate_limit.py) — the recommended intake shape.

• 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 (palinode/api/routers/health.py: subprocess.* call; palinode/cli/_api.py: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (palinode/api/routers/health.py: subprocess.* call; palinode/api/routers/health.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: 9 files (palinode/api/routers/health.py, palinode/cli/__init__.py, palinode/cli/mcp_smoke.py, +6 more) discloses broad/destructive filesystem access: 4 files (palinode/api/routers/health.py, palinode/consolidation/write_time.py, palinode/core/git_tools.py, +1 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.14.0 (minor bump): new capability primitive(s) in source: fs-write, http-client, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, alice, app.example.com, cdn, chat-host, code.claude.com, consol-host, embed-host, env-host, example.com, fallback-1, fallback-2, github, github.com, h, host, lmstudio-host, my-server, ollama, pali.example.net, palinode.test, primary, testserver, vllm-host, x, yaml-host, your-server.

• Transport config

  fail10% of grade

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

  source performs runtime self-update / download-and-execute (bypasses version_behavior); manifest/source references telemetry behavior — disclosure