io.github.frsorrentino/chrome-bridge

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

  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. server/cli.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

  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 (server/launcher.js: imports child_process and calls exec/spawn; server/link-checker.js: outbound HTTP/socket call). discloses shell/exec capability: server/launcher.js: imports child_process and calls exec/spawn discloses dynamic code execution: extension/service-worker.js: uses new Function(…) 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 1.15.1 (minor bump): new capability primitive(s) in source: child_process, dynamic-eval, http-client; new hardcoded outbound host/BCC destination(s): 127.0.0.1, accounts.google.com, chromewebstore.google.com, copycat.example, crm, example.com, github.com, nodejs.org, oauth2.googleapis.com, www.googleapis.com.

• Transport config

  warn10% of grade

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

  sends telemetry to third-party SDK (google-analytics) — disclosure, verify opt-in; manifest/source references beacon behavior — disclosure