Security evidence for the coding tools your team uses.

Use Security evidence for the coding tools your team uses. as a decision directory.

Connect local Code Radar findings to coding-agent workflows, MCP context, repair prompts, and optional CI enforcement without turning review into guesswork. Open the page that matches the concrete decision in front of you, verify its evidence and limits, then continue to the relevant implementation or proof page.

• Scope: Connect local Code Radar findings to coding-agent workflows, MCP context, repair prompts, and optional CI enforcement without turning review into guesswork.
• Evidence: Confirm the supported MCP transport, installation command, permissions, data boundary, finding context, repair prompt, rescan step, and optional CI handoff.
• Boundary: An integration passes deterministic evidence to an agent; it does not make generated fixes trustworthy without review and a clean rescan.

Choose a page by the evidence you need.

For Security evidence for the coding tools your team uses., do not choose from a name alone. Match the page to the repository, reviewer, output, and enforcement point that will determine whether the workflow is useful.

Questions about Security evidence for the coding tools your team uses.

For Security evidence for the coding tools your team uses., these answers define what the directory covers, how to validate a page, and where human judgment remains necessary.

Continue with implementation evidence.

For Security evidence for the coding tools your team uses., use these routes to inspect a real artifact, confirm the product boundary, or implement the workflow described in this directory.