Reviewing Results¶

PostQ provides a shared review experience in the standalone Report Viewer, VS Code, and Eclipse. Reviewers can move from a repository summary to the operation, settings, and source evidence behind a result. Available details depend on the reports loaded.

Repository overview¶

Assessment brings together inventory counts, the five dimensions, and follow-up work. Distribution links open the relevant groups or files with visible, editable filters. This helps you turn a summary into a concrete review selection.

For count definitions and navigation steps, see Assessment Overview.

Individual call review¶

Crypto Functions identifies individual source calls and their available settings. It is useful for investigating a precise source location or checking how a call contributes to a larger operation. See Crypto Functions.

Operation review¶

Operation Groups brings related calls and configuration together. Reviewers can inspect the source sequence, parameters, conflicts, and the separate assessment dimensions before defining a change. The standalone viewer supports file-based collapse in both function and group views. See Operation Groups.

Evidence and reasoning¶

Assessment, reasoning, and remediation details separate the conclusion from its explanation and next actions. Parameter evidence can connect a value's source location to the call that uses it. VS Code provides Crypto Details in its Secondary Side Bar; Eclipse provides embedded details.

For the detailed review sequence, see Interpret Results.

Presets, search, and detailed filters help reviewers select relevant functions or groups by operation, algorithm, assessment, or follow-up need. CSV and JSON exports support a handoff to another team while the complete report folder preserves context.

Controls and loading instructions are covered in Report Viewer. Exchange formats are explained under Sharing Reports.

IDE source links open the relevant file and line. VS Code Problems and Eclipse problem markers make findings accessible during development. Keep the scanned source revision available so that an older report's locations remain meaningful.

Report history and comparison¶

Both IDE integrations retain completed scans and support report comparison. This helps your team investigate how the inventory and findings change after remediation. Compare similar source scope, exclusions, and scanner versions, and test application behavior separately.

Use the VS Code or Eclipse guide for history, comparison, diagnostics, and retention controls.

Migration review¶

The standalone viewer's Experimental Migration Review provides additional scanner-supplied summaries and planning guidance when available. Its experimental scope and controls differ from the function and group review views.