com.anywaypossible/agent-utilities

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 44 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

  warn25% of grade

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

  dependency "@x402/core" is edit-distance 1 from popular package "cors" (typosquat candidate); dependency "@x402/evm" is edit-distance 2 from popular package "ejs" (typosquat candidate); dependency "@x402/mcp" is edit-distance 2 from popular package "yup" (typosquat candidate); dependency "@x402/next" is edit-distance 2 from popular package "jest" (typosquat candidate); dependency "@x402/svm" is edit-distance 2 from popular package "@anthropic-ai/sdk" (typosquat candidate); dependency "geist" is edit-distance 2 from popular package "jest" (typosquat candidate)

• Credential hygiene

  pass15% of grade

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

  No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• Permission scope

  pass15% of grade

  Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

  No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

• Version behavior

  warn10% of grade

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

  vs prior 1.2.0 (minor bump): new tool "recommend_tool" appeared; new tool "merchant_snapshot" appeared; new tool "merchant_audit" appeared; new tool "treasury_preflight" appeared; new tool "payment_guard" appeared; new tool "base_balance" touches a sensitive surface (email/exec/net/fs); new tool "check_url" touches a sensitive surface (email/exec/net/fs); new tool "verify_web_evidence" touches a sensitive surface (email/exec/net/fs); new tool "batch_check_urls" appeared.

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