Status: stub. This document is published early so that researchers have a non-public channel before the project's first tagged release (per DESIGN.md §14). Specific contact details and PGP keys will be filled in by the maintainer before v0.1.0.

Dossier is a local-first CLI tool. The most plausible security concerns are:

• Data exfiltration via the Claude Code conversation. Dossier stores potentially sensitive content (resumes, immigration history, salary, personal statements). All of it is sent to Anthropic's API as part of normal Claude Code operation. This is documented in DESIGN.md §11 and surfaced to the user on first run (forthcoming, M4); it is not considered a vulnerability.
• SQL injection / path traversal in the I/O scripts. All scripts/*.py are thin wrappers over the local SQLite store and the filesystem. A malformed input that lets an attacker read or write outside the project root, or escape the experience schema, is in scope.
• Render escapes in src/renderers/. LaTeX / Typst / DOCX renderers fill templates from content JSON. Any input that produces a payload the renderer interprets as code (rather than data) is in scope.

Out of scope:

• Vulnerabilities in Claude Code, Anthropic's API, Overleaf, or any other third-party service Dossier depends on. Report those upstream.
• Issues requiring write access to the user's machine or git checkout before exploitation.

Please do NOT open a public GitHub issue for vulnerabilities.

Until a dedicated reporting channel is published, contact the maintainer privately via the email listed on the maintainer's GitHub profile (@Jay-00234). Include:

• A description of the issue and the smallest reproduction you have.
• The version (commit hash) you tested against.
• Any suggested mitigation, if you have one.

A response window will be set with v0.1.0. As a stub project, expect best-effort turnaround until then.

Once the issue is confirmed and patched, the fix is merged to main and referenced in the release notes for the next tagged version. Coordinated disclosure timelines can be agreed on a case-by-case basis with the reporter.

(From DESIGN.md §11.3 — not strictly a security policy but worth restating for reporters.)

• Upload user resume data to any hosted service by default.
• Ship analytics or error reporting that transmits content off-machine.
• Auto-update that pulls and runs code without a visible release-notes step.