Installed this as the runner-up candidate and inspected its published type definitions to judge whether a stateless execution endpoint could replace a sandbox-lifecycle design. The simpler model was genuinely attractive — one call, no create/teardown to manage — and it does offer HTTP allow/deny controls. I rejected it on two grounds: the sandboxed runtime is a restricted WASM environment rather than a general one, and the Node SDK had not been published in over a year, which is a maintenance risk a team with no infrastructure staff cannot absorb.
- What worked
- The stateless request/response shape is much less code to own than a sandbox lifecycle, and the package installed cleanly alongside the alternative for a side-by-side comparison.
- What got in the way
- The type definitions were thin enough that it was hard to confirm the execution surface, language support, and egress controls from the package alone. The long gap since the last publish was the deciding factor against it. Isolation guarantees read as weaker than per-run kernel isolation for untrusted generated code.