# Security policy

## Supported versions

Security fixes target the latest `0.2.x` release on the default branch. DeepSeek Harness compatibility is separately limited to the versions documented in the README.

## Report a vulnerability privately

Use GitHub's private vulnerability reporting for this repository:

1. Open the repository's **Security** tab.
2. Choose **Advisories** → **Report a vulnerability**.
3. Include affected versions, reproduction steps using synthetic data, impact, and any suggested mitigation.

Do not open a public issue for a vulnerability and do not attach captured real prompts, tool output, credentials, session files, or other personal/proprietary data. If private reporting is temporarily unavailable, open a public issue that contains no vulnerability detail and only asks the maintainer to enable a private contact path.

## Relevant security boundaries

`dsh-llm-call-inspector` intentionally processes sensitive application content. A report is especially useful when it shows any of the following:

- capture of top-level headers, API keys, abort signals, or undeclared adapter-private request fields;
- cross-session reads, clears, or retention confusion;
- access to the RPC channel by bypassing DSH's Host/Origin fence or browser token/cookie authentication boundary;
- unbounded memory growth or a bypass of configured byte/count ceilings;
- request mutation, response mutation/reordering, duplicate downstream invocation, or swallowed throws;
- unexpected disk persistence or network export of captured bodies;
- browser injection caused by rendering captured JSON; or
- package/install behavior that executes unreviewed code or ships undeclared files.

The following are documented behavior, not vulnerabilities by themselves:

- prompts, tool arguments/results, and model output may contain sensitive values;
- same-user local processes, browser extensions, screen capture, or a compromised Host/browser may observe memory or displayed data;
- records disappear on clear, eviction, reload, disable, uninstall, or restart; and
- provider-native HTTP/SSE data and sessionless calls are outside the plugin's coverage.

See [docs/privacy.md](docs/privacy.md) for the complete data-handling model.