Security policy

English · 简体中文

Supported version

Only the latest 0.1.0-alpha.x source preview is maintained. DeepSeek Harness is also prerelease software, so every upgrade must rerun the compatibility and loader tests recorded in DSH_COMPATIBILITY.md.

Reporting a vulnerability

Do not place credentials, private conversations, database extracts, or working exploits in a public issue. Use GitHub private vulnerability reporting. If that channel is unavailable, publish only a content-free description asking the maintainers to establish a private channel.

Security boundaries

• Recalled memories are untrusted read-only background. They do not grant instructions, permissions, identity, or tool authority.
• Retrieval is restricted by exact user, agent, and workspace scopes.
• Recall and memory-tool outputs are excluded from ingestion to prevent self-amplifying archive feedback.
• Credentials belong in environment variables, never Cordis YAML, fixtures, logs, or issue reports.
• Memory databases and native Harness session logs may contain highly sensitive data and require ordinary filesystem protection.

Known gaps

The alpha release has no authentication or administration UI of its own, no selective-forgetting workflow, no persisted operational metrics endpoint, and no production-scale vector index. Multi-user deployments and untrusted shared machines are outside the supported scope.