Safety & Security

Custom Driver Execution #

Custom node drivers can be registered dynamically at runtime. When dynamic node definitions are compiled, the registry evaluates their implementation via standard JavaScript mechanisms:

• Dynamic Compilation: The runtime compiles graph-supplied string processes using the new Function constructor via registerCustomDrivers. Graph-supplied string processes compile in the current JavaScript realm, not a guaranteed main or "host" thread. Ordinary registered drivers and handler modules are not all dynamically compiled.
• No Sandbox Isolation: The engine does not provide a VM boundary, worker sandbox, or secure execution container. Custom drivers, lifecycle hooks, and handlers run in the current JavaScript realm with the ambient authority available there.
• Ambient Authority: Graph custom drivers run with the ambient capabilities of the current realm. Handlers are ordinary trusted imports. They do not have arbitrary lexical host-variable access.

Security Boundaries & Credentials #

Protecting sensitive API keys, tokens, and data fields is the responsibility of the host application:

• No Native Credential Protection: The runtime does not automatically scrub, encrypt, or hide credentials that are written directly into a graph's JSON representation. Storing raw credentials in graph parameters makes them serializable and visible.
• External Key Management: Keep authentication credentials outside serialized graph data. Graph parameters may contain arbitrary values; when a node needs a credential, store a non-secret reference identifier and let host-owned handlers or providers resolve it outside graph data.

Authority Boundary #

// Store a non-secret reference
const referenceParams = {
  voice: 'en-male-1',
  credentialRef: 'voice-provider/primary'
};

Engine neither validates nor resolves this reference; a host-owned resolver does so under host policy.

Network Boundaries & GraphServer #

The library includes a development server for synchronization sessions, which can be imported via:

import { createServer } from 'symbiote-engine/GraphServer.js';

When utilizing this server primitive, hosts must be aware of the following security limitations:

• Wildcard Origin Policy: The development server operates with unrestricted wildcard CORS (Access-Control-Allow-Origin: *) and any-origin WebSocket connections.
• No Authentication: The server lacks built-in authentication, authorization, rate limiting, request validation, or TLS encryption.
• Remote Mutate/Execute Capability: Because the server exposes endpoints that allow remote connections to edit and execute graphs, exposing it directly to public networks is dangerous.