io.github.LeonTing1010/tap

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

  warn25% of grade

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

  server instructions: off-vendor URL in a description (taprun.dev); capability text should not name where data goes.

• Supply chain

  warn25% of grade

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

  install hook "postinstall" present and not a recognized benign build command; package name "@taprun/cli" is edit-distance 2 from popular package "chai" (typosquat candidate)

• 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. bin/postinstall.js) — 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: shell/exec capability AND destructive filesystem writes together (bin/postinstall.js: imports child_process and calls exec/spawn; bin/tap.js: path traversal ('../') combined with file access). discloses shell/exec capability: bin/postinstall.js: imports child_process and calls exec/spawn discloses shell/exec capability: bin/tap.js: imports child_process and calls exec/spawn discloses broad/destructive filesystem access: bin/tap.js: path traversal ('../') combined with 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 0.20.7 (minor bump): new tool "capture" touches a sensitive surface (email/exec/net/fs); new tool "verify" touches a sensitive surface (email/exec/net/fs); new tool "mark" appeared; new tool "run" touches a sensitive surface (email/exec/net/fs); new hardcoded outbound host/BCC destination(s): chromewebstore.google.com; new install hook(s) not present in prior version: postinstall.

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