Choose an Interface¶
All scanning interfaces call the same scanner backend and produce the same deterministic report contracts. Choose an interface for workflow fit, not for different detection behavior.
| Interface | Choose it when | Host requirements |
|---|---|---|
| Command Line | You need scripts, local automation, or CI control | Java and OpenGrep |
| VS Code | Developers need scans, report history, Problems, and source navigation | VS Code, Java, OpenGrep |
| Eclipse | Eclipse or Spring Tools teams need project scans and report review | IDE, Java, OpenGrep |
| Container Runner | You need a fixed non-interactive Linux runtime | Docker or Podman |
| Report Viewer | Reviewers need completed reports but should not run scans | Desktop browser |
| CI/CD | You need repeatable repository scans and retained evidence | CLI or container runner |
Shared behavior¶
- The backend owns detection, assessment, grouping, and generated output.
- The offline license gate runs before scanning in every scanning host.
- The Report Viewer is read-only and does not require activation.
- A finding does not cause a nonzero process exit by itself.
- Report data can contain source paths and code evidence and should be handled as sensitive engineering information.
For a first evaluation, use Quick Start.