Audit sandbox-runtime production dependency advisories before npm publication #383

Evidence

The worker production install currently resolves:

• @anthropic-ai/sandbox-runtime@0.0.75
• node-forge@1.4.0 through sandbox-runtime (^1.4.0)
• zod@3.25.76 through sandbox-runtime (^3.24.1)

npm audit --omit=dev reports three high-severity package entries: the two concrete dependency advisories and sandbox-runtime as the affected parent. These versions are already present before #377; the release PR does not introduce them.

Node-forge is used in sandbox-runtime’s MITM certificate modules, and Zod is used in its sandbox configuration parser. This confirms dependency use, not exploit reachability for each advisory.

Follow-up

• Evaluate a compatible patched node-forge resolution and rerun native sandbox/network tests on Linux and macOS.
• Track the upstream sandbox-runtime migration or fix for the Zod advisory. Do not force Zod 4 into its Zod 3 API without compatibility tests.
• Determine which advisories are reachable through the worker configuration and certificate paths, and record any non-applicable cases.
• Re-run the production audit and packed-consumer smoke checks before promoting a worker npm release.

Public advisories

• GHSA-mrhx-c7xc-m3w5
• GHSA-86w9-cpqp-85rv
• GHSA-4642-5mcj-2rqw
• GHSA-6wvx-3r32-xmcg

No dependency versions were changed as part of the import sync.