CodeCortex processes source code and may store local project state, traces, indexes, and benchmark artifacts. Treat those inputs and artifacts as potentially sensitive.

During alpha, security fixes target the latest release and current main.

Do not open a public issue for suspected vulnerabilities. Use GitHub Security → Report a vulnerability / the private security-advisory flow. Include the affected version or commit, reproduction steps, impact, and suggested mitigation when known.

The project aims to acknowledge credible reports promptly, coordinate remediation privately, and publish an advisory after a fix is available when disclosure is appropriate.

• Project state stays under .codecortex/.
• The dashboard binds to 127.0.0.1 by default.
• Core operation does not require a remote service.
• External adapters are disabled unless explicitly configured.
• Backend commands execute without a shell.
• Semantic edit paths are constrained to the project root.
• Optional external engines run with an explicit argument vector, a resolved absolute executable, a bounded timeout, and a bounded output size.
• Dependency documentation lookups are disabled by default. When enabled they transmit only a library name, a resolved version, and the user's question; repository source, paths, secrets, Git history, and memory are never sent.
• Documentation API keys are read only from a configured environment variable, are never persisted to project state or traces, and are redacted from diagnostics.
• Structural rewrites require a preview, re-verify every file's content hash before writing, enforce file/match/byte limits, write atomically, and roll back on partial failure.
• Task traces redact common credential/token fields.
• Agent configuration is merge-safe and refuses malformed configuration.
• Secrets should never be deliberately stored in project or team memory.

CI includes dependency auditing, Bandit, security-boundary tests, CodeQL, dependency review, OpenSSF Scorecard, coverage reporting, CycloneDX SBOM generation, signed release payloads, and build provenance attestations.

Release artifacts include checksums and provenance. Consumers should verify release artifacts and avoid installing unreviewed forks or mutable source references in security-sensitive environments.