Why
KShield currently only has editor coverage in VS Code. JetBrains IDEs (IntelliJ, PyCharm, WebStorm) cover a large share of the other half of the developer market with the same value prop: inline warnings, secret detection, one-click fixes powered by the local backend.
Proposed scope
- Mirror the VS Code extension's feature set against the same local backend API (
/api/v1/scan, /api/v1/actions/*):
- Scan current file command
- Inline gutter/line warnings
- Apply suggested fix
- Suppress rule
- Backend connection status check
- Built as a JetBrains plugin (Kotlin, using the IntelliJ Platform SDK).
Priority note
Lower priority than the MCP server and CI Action — revisit once there's user signal (support requests, community asks) specifically for JetBrains support.
Why
KShield currently only has editor coverage in VS Code. JetBrains IDEs (IntelliJ, PyCharm, WebStorm) cover a large share of the other half of the developer market with the same value prop: inline warnings, secret detection, one-click fixes powered by the local backend.
Proposed scope
/api/v1/scan,/api/v1/actions/*):Priority note
Lower priority than the MCP server and CI Action — revisit once there's user signal (support requests, community asks) specifically for JetBrains support.