Skip to content

Eclipse

The PostQ Eclipse plugin hosts scanner-service in Eclipse and Spring Tools. It provides project scans, report history, report comparison, source navigation, console output, and problem markers from backend-generated findings.

Install and configure

The beta artifact is an Eclipse PDE project package rather than a p2 update site. Follow the README inside postq-code-scanner-eclipse-plugin-<version>.zip, then open:

Window > Perspective > Open Perspective > Other > PostQ Crypto Readiness

Set scanner-service, OpenGrep, language, history, and Offline license file preferences under:

Window > Preferences > PostQ Crypto Readiness

Run scans

Use the Project Explorer or Package Explorer PostQ Code Scan menu:

  • Scan Project
  • Scan All Projects
  • Stop Running Scan
  • Show Report
  • Open Reports Folder
  • Compare Latest With Previous
  • Show Console
  • Configure

Review history

The Reports view uses projects as parent nodes and completed scans as child nodes. Double-click a scan to open PostQ Code Scan Report. Select two scans from the same project and choose Compare Reports to open the comparison view.

The plugin reads backend reports and must not be used as a separate source of risk or compliance logic. Report rows can navigate to source when the project and path remain available.

Browser component

Report views use the Eclipse SWT Browser on a loopback-only local host. On Windows, a current Microsoft Edge WebView2 runtime may be required by the selected SWT browser backend. Enterprise desktop teams should include the browser runtime in their Eclipse workstation baseline.

If the report remains blank, review the Eclipse Error Log, PostQ console, and Troubleshooting.