Security and deployment

Self-host runtime assets

• Pin package, Worker, Wasm, font, and codec versions together.
• Serve assets from the same trusted deployment boundary as the host application.
• Use artifact hashes and signatures from the release manifest.
• Do not place license signing secrets or other application secrets in browser code.

Treat every document as untrusted

Parsing runs with bounded archive, XML, image, object, render, and time budgets. Active content is blocked rather than executed. Applications should still apply their own upload policy, size limits, authentication, content security policy, and incident response.

Support files are a separate flow