All tutorials

Findings in the editor

Cordon 0.7.02 sections · 1 diagramView this tutorial on GitHub

Cordon's findings where you are already looking -- on the line, with the fix beside it -- in VS Code and the editors built on it, and in every JetBrains IDE. Both run the cordon-scanner you installed; neither sends anything anywhere.

Findings in the editor, figure 1
┌──────────────────────────────────────────────────────────────────────────────────┐
│  install       pipx install cordon-scanner, then the extension for your editor   │
│                                                                                  │
│  VS Code       the Visual Studio Marketplace: "Cordon supply-chain scanner"      │
│  Cursor,       Open VSX, the same extension                                      │
│  Windsurf,                                                                       │
│  VSCodium                                                                        │
│  IntelliJ,     the JetBrains Marketplace: "Cordon Supply-Chain Scanner"          │
│  PyCharm,      (2025.1 and later)                                                │
│  WebStorm,                                                                       │
│  GoLand, ...                                                                     │
│  offline       the .vsix and the plugin .zip are on every release page           │
│                                                                                  │
│  it runs       on opening a project, after a save, and on demand                 │
│  it never      runs in a folder you have not trusted, or lets a repository       │
│                choose what it executes                                           │
└──────────────────────────────────────────────────────────────────────────────────┘
settingdefault
cordon.pathcordon-scannermachine setting only: a workspace cannot change it
cordon.scanOnSavetrue
cordon.minimumSeveritylowfindings below this are not shown
cordon.mcp.enabledtrueoffer Cordon's MCP server to the editor's agents
cordon.mcp.allowOnlinefalsemachine setting only: let those tools use the network

On VS Code 1.101 and later the extension also registers Cordon's MCP server with the editor, so Copilot's agent mode and any other agent that reads VS Code's MCP servers can check packages, install commands, skills and MCP servers before acting (tutorial 30) -- with no configuration file. On an editor without that API, Cordon: Show MCP configuration prints what to add.

Findings without a line -- repository-wide ones, or members of an archive -- go to the Cordon output channel, and the status bar shows the count.

Findings are marked on their lines and listed in the Cordon tool window (double-click opens the line). Tools > Scan Project with Cordon rescans; Settings > Tools > Cordon holds the scanner's path, the minimum severity and rescan-on-save, kept with the IDE, never with a project. Tools > Copy Cordon MCP Configuration puts the configuration for AI Assistant on the clipboard, to paste under Settings > Tools > AI Assistant > Model Context Protocol (MCP).

Next: 21 · Reviewing a dependency update.