# Security Policy

## Supported versions

Security fixes are applied to the latest release on the default branch while the project is in developer preview.

## Reporting a vulnerability

Do not open a public issue for a vulnerability that could expose credentials, execute source-plugin code, escape the output directory, or silently widen DSH permissions.

Use GitHub's private vulnerability reporting for this repository. Include:

- the affected dsh-compat version or commit;
- a minimal source-plugin fixture with secrets removed;
- expected and actual behavior;
- whether inspection, conversion, or generated-bundle execution is involved.

## Trust model

Source plugins are untrusted input. `inspect` and `convert` must not run source lifecycle scripts, hooks, binaries, MCP servers, or LSP servers. Unknown executable semantics and permission widening fail closed.

Generated bundles are code and configuration intended for review before installation. dsh-compat does not attest that an upstream plugin or MCP server is safe to execute.