Skip to content

v2.1.2 — security: 0 vulnerabilities, declared capabilities, SSE warning

Latest

Choose a tag to compare

@PaulieB14 PaulieB14 released this 09 Aug 15:36

Response to the ClawHub security audit of 2.1.1. One finding was a false positive; four were worth acting on.

Dependencies: 9 vulnerabilities → 0

npm audit now reports 0 vulnerabilities, down from 9 (6 high). The cleared packages were all transitive: hono, express, path-to-regexp, fast-uri, body-parser, qs, ip-address, express-rate-limit, @hono/node-server.

The @modelcontextprotocol/sdk floor is raised ^1.12.1^1.30.0, so a fresh install can no longer resolve the version the audit flagged.

Capabilities are now declared, not implicit

The skill manifest states exactly what this server touches:

  • One env varGRAPH_API_KEY, sent only to gateway.thegraph.com, never forwarded to Polymarket
  • Three hostsgateway.thegraph.com, gamma-api.polymarket.com, clob.polymarket.com
  • No filesystem access

Anything outside that list is a bug.

SSE transport carries a warning

The optional --http transport is unauthenticated: anyone who can reach the port can call every tool and spend the operator's GRAPH_API_KEY quota. Both README and SKILL.md now say so plainly, and point at stdio — which has no network surface — as the better default.

On the "critical exposed secret"

The audit flagged smithery.yaml:16 as a hardcoded credential. That line is:

env: config.graphApiKey ? { GRAPH_API_KEY: config.graphApiKey } : {}

A template passing the user's own config value into an env var. No credential is present. Noted here rather than silently ignored, in case anyone reads the audit before the code.


No functional changes. 35 tools, verified over stdio after the dependency updates.