secutils-deno-runtime

To write JavaScript for Secutils responder scripts, you must target the restricted Deno sandbox runtime, which defines specific global context shapes and limits available APIs. This ensures your code executes safely within the Secutils environment.

The context global shape in the Deno runtime sandbox provides script-specific input data and state for responder scripts and API tracker configurators. It structures how your JavaScript receives parameters and environment details from Secutils.

Standard btoa and atob functions are unavailable in the restricted Deno runtime sandbox, so you must use provided pure-JavaScript replacements for Base64 encoding and decoding. This ensures compatibility when processing data in Secutils scripts.

To forward HTTP requests safely from an API tracker script sandbox, use the op_proxy_request API provided by the Deno core namespace. This mechanism allows your restricted JavaScript to communicate externally without compromising the sandbox environment.

Responder scripts fail when accessing standard Deno APIs because the execution environment is a restricted Deno runtime sandbox that explicitly limits available namespaces. You must reference the Deno.core utility namespace to find permitted operations.

Yes, you need prior knowledge of Deno and JavaScript to configure API tracker scripts in Secutils. The runtime requires understanding sandbox limitations, body auto-conversion to bytes, and specific context globals to write functional script code.