Sandbox Runtime API v0.1.2

Sandbox Runtime API v0.1.2

Security maintenance release for the public 0.1 protocol. This archive contains the Provider diagnostic/failure data-minimization fixes previously available only on main; older release archives remain unchanged.

Source: 9228de5fead2ff055b58735b6eebead4ad7ca4dd, through PR #10. The tested candidate and merged source trees are identical.

Changes

• Replace Provider exception and stored failure details with fixed public messages; preserve legal portable error codes and normalize arbitrary codes.
• Suppress Provider exception text in conformance reports, reject endpoint userinfo credentials, and avoid reflecting invalid Provider states.
• Verify installed-distribution exception/failure redaction, exact supplied archives, safe paths, package identity, and all five diagram integrity hashes.
• Separate fixture startup/setup headroom from unchanged scanner, Provider and cancellation deadlines; assert owned descendant readiness and cleanup; bound test worker concurrency without skipping cases or reducing coverage gates.
• Update bilingual documentation, release installation, public safety guidance, security policy and changelog.

Verification — 2026-10-14

All 202 tests across 11 files passed in normal and coverage runs locally and in required Node.js 22/24 PR CI and merged-main CI. Coverage: 90.66% statements, 86.14% branches, 93.59% functions, 93.03% lines. Lint, types, build, 26 Markdown/19 managed document IDs, installed package and dependency gates passed; the audit reported no known vulnerabilities at verification time.

Source/available-history/media scans and new author/committer identity range checks passed. Independent source soft matches were reviewed as synthetic/public fixtures. Legacy commit identities remain a separate owner-reviewed issue; no old-history erasure, isolation or production-security certification is claimed.

The exact release archive passed independent offline installation, compiled consumer types/example, real SDK/CLI/SSE/shutdown checks, installed Provider exception/stored-failure redaction, all 76 entries and five visual integrity hashes. The extracted distribution passed both the project public-content scanner and an independent publication scan with no matches. A prior online consumer-install timeout was not counted as success; the passing check used an isolated offline npm cache.

Publication read-back passed: both GitHub attachments were downloaded and matched the tested originals byte-for-byte, checksum verification passed, and a second isolated installation/type/example/SDK/CLI/SSE/shutdown/Provider-redaction run passed against the downloaded archive. The release tag resolves to the exact source commit above. The original v0.1.0/v0.1.1 tag targets and v0.1.1 attachment digests were verified unchanged. GitHub reported zero open secret-scanning and Dependabot alerts at verification time. Branch protections were preserved.

Install

Download the archive and checksum file into the same directory:

shasum -a 256 -c SHA256SUMS.txt
npm install --ignore-scripts ./sandbox-runtime-api-0.1.2.tgz
npx sandbox-runtime serve --host 127.0.0.1 --port 4311

SHA-256: 751365ee8eee5c166a5baadc1e2faf5b553cf1e2c6654c123fb78b8ca689438b.

The CLI uses the unsafe Local Provider and host-user permissions. Run trusted synthetic development commands only, never untrusted or AI-generated code. No cloud deployment or npm registry publication is included; the archive remains private: true with no production dependencies. Intentionally returned command output/file bytes and approved metadata are not automatic secret-redaction surfaces.