🇬🇧 English | 🇹🇷 Türkçe

• Current packaged release line: 0.2.x (package.json, CHANGELOG.md)
• Older release-line support policy: requires maintainer confirmation

mcp-code is designed to keep risky operations bounded:

• It does not expose generic shell execution as a public tool.
• It does not expose raw file CRUD as a public tool.
• It limits edit application to previously planned scope.
• It limits verification to configured commands and allowed workspace roots.

See docs/en/security/security-model.md for the detailed model.

Please do not open a public issue for security reports.

Use this channel instead:

1. GitHub Security Advisories for this repository.

No separate private security contact is documented in this repository today. If that changes, update this page and SUPPORT.md together.

Include:

• A short summary of the issue.
• Reproduction steps.
• Impact and likely blast radius.
• Suggested mitigations if you have them.

• Initial triage target: within 3 business days.
• Status update target: within 7 business days.
• Fix and disclosure timeline depends on severity, exploitability, and release coordination.

• Stdout is reserved for MCP protocol traffic.
• Logging goes to stderr.
• New tools must preserve the semantic workflow boundary.
• New config fields must be documented.
• Verification commands must stay explicitly allowed.

Last updated: 2026-03-10