v5.5.7 — socket.json shellAccess False-Positive Fix

Type: Chore / Supply Chain

v5.5.7 — socket.json shellAccess False-Positive Fix

Type: Chore / Supply Chain Date: 2026-05-18

What changed

Added shellAccess ignore entries to socket.json for AgentRuntime and McpToolConsumer.

Root cause: Socket.dev uses two distinct alert type IDs for child_process usage:

• shellExec — triggered by shell command execution calls (e.g. execFile, execSync)
• shellAccess — triggered by the child_process module import itself

Both files were already documented under shellExec (v5.5.6 and earlier). The shellAccess alert type requires a separate ignore entry.

Why these files use child_process:

• AgentRuntime (lib/agent-runtime.ts) — ShellExecutor uses child_process.spawn for sandboxed command execution. Shell access is opt-in only; the caller must explicitly configure and enable the ShellExecutor with a SandboxPolicy.
• McpToolConsumer (lib/mcp-tool-consumer.ts) — uses child_process.spawn to launch MCP server subprocesses for stdio-based MCP transport. The MCP stdio protocol requires process spawning; the caller provides the server command.

Files changed

• socket.json — four new shellAccess ignore entries added
• Version bumped to 5.5.7 in package.json, skill.json, openapi.yaml, README.md, and all 12 doc/config files.

No code changes. All 3,093 tests continue to pass.