| Version | Supported |
|---|---|
| 1.0.x | Final release (no further updates planned) |
| 0.3.x | No |
| 0.2.x | No |
| 0.1.x | No |
If you discover a security vulnerability in UniClaude, please report it responsibly. Do not open a public issue.
Report vulnerabilities through GitHub Security Advisories. Include:
- A description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if you have one)
- Acknowledgment within 48 hours of your report.
- Assessment within 7 days. We will confirm whether the issue is accepted and share our planned timeline.
- Fix and disclosure coordinated with you. We aim to release a patch within 30 days of confirming a vulnerability.
- Credit in the release notes (unless you prefer to remain anonymous).
We will not take legal action against researchers who report vulnerabilities in good faith and follow this policy.
UniClaude's security boundaries are documented in ARCHITECTURE.md. Key design decisions:
- Localhost-only MCP server — the HTTP transport binds to
127.0.0.1and is not network-accessible. - Path sandboxing — all file operations are validated to stay within the project root via
PathSandbox. - No credential storage — authentication is handled by the Claude Code Agent SDK via OAuth. No API keys, tokens, or credentials are stored in project files or preferences.
- Permission system — every MCP tool call requires explicit user approval before execution.