← All agent-stack verdicts

Sandboxed code execution

Adopt and wrap Confidence Medium Group Tools and environment Evidence as of 2026-09-23

Written by VerdictsTools · Reviewed by ReviewTools on 2026-09-23 (separate AI agent sessions; review record)

Bracketed tags are evidence tiers from RULEBOOK.md §1: [Verified] means checked directly, [CI-observed] read from a project’s CI pages, [Maintainer claim] asserted by the project, [External] a dated third-party source, [Inference] our judgment. A gold path:line link opens the cited line. TRL is technology readiness level, scored 1 to 9. CI is continuous integration: automated checks that run on every push. To pin is to freeze a dependency, oracle, or assessment at an exact commit or version, so later changes cannot silently alter what was checked. The rider is the license clause withholding all rights, including benchmarking and testing, from OpenAI, Anthropic, their affiliates, and anyone acting for them; most FrankenSuite repos carry it.

Bottom line

Inference, medium confidence: adopt a maintained isolation substrate (Firecracker microVMs, gVisor, or Kata) or an agent SDK that delegates isolation to a substrate (E2B on Firecracker microVMs; Cloudflare Sandbox SDK on Cloudflare's own edge substrate), and wrap it with isolation tests of your own. Writing your own isolation layer would recreate years of adversarial test work, but no repository in the evidence publishes a sandbox-escape test suite, and the agent-facing SDKs test their API layer while leaving isolation to the substrate. Before you claim "contained", write the threat model, pin the substrate and guest image by hash, and run a red-then-green confinement suite against that pin.

Adopt, do not rebuild

License checked on 2026-09-23; non-permissive licenses are named in the text.

Copy these practices

Build only if

  • Your threat model requires running native code inside one process, where microVM and application-kernel substrates do not fit, as with a from-scratch engine's JIT path. Even then, the capsule packet names V8's in-process sandbox as the deployed reference, which a from-scratch engine cannot borrow, and Wasm runtimes as the way to avoid running native code at all. [Inference] (packets/franken_native_capsule-assessment.md:65 a classic V8-sandbox-shaped problem, scoped here to a from-scratch engine; packets/franken_native_capsule-assessment.md:151 FrankenEngine is not V8 and cannot borrow it; packets/franken_native_capsule-assessment.md:152 is to not run native code at all — run Wasm through a validated compiler)
  • A host without KVM does not by itself justify building: the Firecracker battery depends on KVM, and gVisor is the evidenced non-microVM paradigm (the pack does not record whether gVisor needs KVM; check its platform options before relying on it). [Inference] (ecosystem/pickup/pickup-sandbox-exec.md:391 security/performance battery (Buildkite-hosted, KVM-dependent); ecosystem/pickup/pickup-sandbox-exec.md:138 Two isolation paradigms coexist as norms for the type)
  • License gives no reason to build: a fresh read on 2026-09-23 (gh api repos/<owner>/<repo> --jq .license.spdx_id, plus the LICENSE file for cloudflare/sandbox-sdk, where the API said NOASSERTION) returned Apache-2.0 for all five adopted repositories. [Verified] (stack/METHOD.md:79 Check the license of everything you tell a builder to adopt)

Where FrankenSuite touches this

What we cannot say

Revisit when

  • A maintained, version-pinned public sandbox-escape vector suite appears, or an agent SDK (E2B, Cloudflare, Vercel) publishes escape tests at its own boundary.
  • Daytona's core development returns to a public repository, or vercel/sandbox shows sustained maintenance.
  • franken_native_capsule gains a consumer and its planned mutation harness, or franken_remote's decoder escape test is observed running.

Sources

Starting a build here?

Begin from the pickup companion for Sandboxed code execution: it carries the charter seed, the oracle candidates and how to verify them, and the first claims to register, so a new project starts from evidence instead of from scratch.

Help fix it

Each opens a GitHub issue form with this page’s address filled in. You need a GitHub account.

Made by Joshua Nowak (ZestStream) with AI coding agents. Not affiliated with or funded by Jeffrey Emanuel; Joshua uses his public tools and is a paying subscriber to jeffreys-skills.md.

Source on GitHub MIT licensed