Skip to content

feat(iac): scan Infrastructure-as-Code files for misconfigurations#47

Merged
tembleking merged 1 commit into
masterfrom
feat/iac-scanning
Jul 15, 2026
Merged

feat(iac): scan Infrastructure-as-Code files for misconfigurations#47
tembleking merged 1 commit into
masterfrom
feat/iac-scanning

Conversation

@tembleking

Copy link
Copy Markdown
Member

Adds IaC scanning so the LSP can flag misconfigurations, not just image vulnerabilities. This is the biggest feature the VSCode extension had that the LSP lacked, and a prerequisite for the LSP becoming the extension's core engine.

The scanner runs sysdig-cli-scanner --iac over a single file (via a "Scan IaC file" code lens on Compose/K8s manifests) or the whole workspace recursively (sysdig-lsp.execute-iac-scan with no argument), and publishes findings as per-file diagnostics.

Diagnostics are now source-tagged (sysdig-iac vs sysdig-vuln) so IaC and image-scan results have independent lifecycles on the same document: each scan replaces only its own findings, and document edits clear line-anchored vulnerability diagnostics while preserving IaC ones. Command execution was moved off the server lock so a long recursive scan no longer stalls unrelated editor requests.

Also fixes the Neovim config examples in the README, which named the wrong environment variable (SYSDIG_API_TOKEN instead of SECURE_API_TOKEN), and documents the token fallback across all editors.

Bumps to 0.9.0.

@tembleking
tembleking enabled auto-merge (squash) July 15, 2026 13:25
@tembleking
tembleking merged commit 5a0df08 into master Jul 15, 2026
5 checks passed
@tembleking
tembleking deleted the feat/iac-scanning branch July 15, 2026 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants