Until the first stable release, security fixes target the latest 0.x version on main.

Use the private vulnerability reporting form; the maintainer must keep GitHub private vulnerability reporting enabled for supported releases. If that form is unavailable, contact the maintainer privately through the GitHub profile instead of opening a public issue. Do not include secrets, private media, or exploit payloads in a public discussion. Reports should receive an initial acknowledgement within 72 hours.

• The preview server binds only to loopback and sends the browser a path-free project representation.
• Markdown is parsed and sanitized; terminal and UI fields are escaped.
• Scene, theme, attachment, ANSI, and asciinema paths are confined to the physical project root, including symlink resolution.
• Terminal events are display data. Termotion never executes commands from a scene.
• Chrome and FFmpeg are local trusted executables. Override environment variables should point only to binaries you trust.
• Chrome sandboxing remains enabled by default. TERMOTION_CHROME_NO_SANDBOX=1 is an explicit escape hatch for isolated containers only and weakens browser process isolation.
• Output locations are user-selected and protected from silent overwrite. With --force, PNG cleanup is limited to generated frame names and the manifest; unrelated files still block the render.

The project format can reference local fixture contents, so review third-party projects before rendering and avoid putting sensitive data into fixtures or manifests.