io.github.aarwitz/tapp

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.

  repository linkage verified

• Credential hygiene

  warn15% of grade

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

  mcp-server/src/application-model.js: assigns a literal to password (TEST…RD (len 13)) — non-provider secret literal; prefer environment intake. mcp-server/src/index.js: assigns a literal to password ($TES…RD (len 14)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. mcp-server/src/browser-product.js) — 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 (mcp-server/src/android-driver.js: imports child_process and calls exec/spawn; browser/app.js: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (mcp-server/src/android-driver.js: imports child_process and calls exec/spawn; mcp-server/src/android-driver.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename)). discloses shell/exec capability: 16 files (mcp-server/src/android-driver.js, mcp-server/src/browser-product.js, mcp-server/src/browser-workspaces.js, +13 more) discloses dynamic code execution: mcp-server/src/web-explorer.js: uses eval(…) discloses broad/destructive filesystem access: 27 files (mcp-server/src/android-driver.js, mcp-server/src/android-explorer.js, mcp-server/src/android-flow.js, +24 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.17.3 (patch bump): new capability primitive(s) in source: child_process, dynamic-eval, fs-write, http-client; new hardcoded outbound host/BCC destination(s): 127.0.0.1, api.anthropic.com, example.test, github.com, runtapp.com, tapp.invalid.

• 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.