This project is pre-release. Security fixes are applied to the latest master branch only (currently 0.1.0.dev0).

Please do not open public GitHub issues for security vulnerabilities.

Primary path (always works): Contact a repository maintainer through a private channel you already use with the project (for example a direct message or private email). Include steps to reproduce, affected version/commit, and impact.

GitHub Security Advisories (when enabled): Once Private vulnerability reporting is turned on for this repository (Settings → Security → Private vulnerability reporting), external researchers may use the private advisory form. If that link returns 404 or the form is unavailable, use the primary path above — the advisory URL only works when the setting is enabled.

Repository admins: Enable private vulnerability reporting before merge if you want the advisory form to be the default reporter path; until then, maintainers should treat the primary path as authoritative.

Timelines may extend for complex issues; we will keep reporters informed.

Security issues in this repository that affect users of the default local setup:

• Path traversal — session and export paths resolved via safe_join in utils/session_path.py
• Cross-site scripting (XSS) — rendered session HTML in static/js/ (mitigated by DOMPurify + SRI in static/index.html)
• Export integrity — bulk zip and per-session export in api/export_api.py and utils/export_engine.py
• Local file boundaries — read-only access to ~/.claude/projects/; writes limited to export output and app state
• Debug-mode exposure — Flask/Werkzeug debugger when --debug is combined with a non-loopback --host (blocked at startup in app.py)
• Information disclosure — API error responses scrub internal exception details (see api/error_codes.py)

• Intentional network-facing deployment — this tool is designed for local browsing on loopback; exposing it on untrusted networks is not a supported configuration
• Upstream Claude Code JSONL format bugs — malformed or hostile data from Claude Code itself (we harden parsing but do not guarantee full isolation from arbitrary JSONL)
• Third-party CDN availability — DOMPurify is loaded from cdnjs with SRI; CDN compromise is an infrastructure concern outside this repo