io.github.benseverndev-oss/goldenflow

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

  pass25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  Scanned 10 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.

• 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. goldenflow/cli/main.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 (scripts/build_native.py: subprocess.* call; pyproject declares an HTTP client dependency). has both shell/exec and destructive filesystem writes (scripts/build_native.py: subprocess.* call; goldenflow/config/loader.py: open(…, 'w'/'a'/'x') write-mode file access). discloses shell/exec capability: scripts/build_native.py: subprocess.* call discloses broad/destructive filesystem access: goldenflow/config/loader.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

  fail10% of grade

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

  vs prior 2.1.0 (minor bump): new tool "echo" appeared; new tool "add" appeared; new tool "server_time" appeared; new capability primitive(s) in source: fs-write, subprocess; new hardcoded outbound host/BCC destination(s): a.com, avatars.githubusercontent.com, bensevern.dev, benzsevern.github.io, example.com, foo.com, github.com, not-gcs, not-s3, sub.domain.org, test.org, www.example.com, www.test.org, x.com.

• Transport config

  fail10% of grade

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

  remote MCP endpoint declares NO authentication (unauthenticated remote — nginx-ui/CVE-2026-33032 class); manifest/source references tracking behavior — disclosure