Small surface. Clear boundaries.

Input is data, never instructions.

Pasted code and commands are not executed. Output is rendered as text. Tool-specific limits and bounded computation are required before a tool is published.

Protection around the interface.

The application uses a Content Security Policy with fresh per-request script nonces, restricted resource origins, and no production eval or unrestricted inline scripts. No transformation API or remote URL proxy is present.

Dependencies are part of the product.

Versions are pinned and changes are checked through tests, dependency scanning and review. A successful build is not a security certification.

Keep reports free of secrets.

If you encounter an issue, record the page and the steps using a small invented example. Never include passwords, access tokens, private source code or personal data. A monitored private reporting channel must be configured before public launch.