Reading findings

When a run completes, open it in Runs and switch to the Findings tab. The findings view is designed to answer four questions quickly:

1. What is the issue?
2. Where is it?
3. Can it be reproduced?
4. How should we fix or triage it?

Findings list

The list groups findings by severity, and by cluster where applicable. Each row includes the core information for a first triage pass:

• the severity tag,
• the finding number, such as F-001,
• the finding title, and
• the current validity state.

Use the filters above the list to narrow by severity, validity, target, or free-text search.

Finding details panel

Selecting a finding opens the detail panel. The panel always starts on the Finding tab and may also include Proof of concept and Remediation tabs when that content exists.

Finding tab

The main explanation view. Depending on the result, it can include a plain-language description, affected files, contracts, functions, or other targets, detailed technical analysis, grouped or deduplicated context, and automated triage notes.

Proof of concept tab

Shows the exploit artifact or reproduction details V12 generated for the finding. Treat it as evidence that the issue was pushed beyond static suspicion into something concrete enough to execute or demonstrate.

Remediation tab

Shows remediation guidance, which may include an explanation of the proposed fix, a patch, and validation output.

A validated remediation means V12 re-checked the exploit path against the proposed fix and confirmed the original exploit no longer succeeds.

Review controls

You can review a finding directly from the list or the details panel.

Severity

Use the severity tag dropdown in the list to change the risk level for your team.

Validity

Mark a finding as valid, invalid, acknowledged, or unreviewed. In the details panel, clicking an already-active validity button resets the finding back to Unreviewed.

Team notes

Use Add a note to leave review context, handoff details, or follow-up items. Notes are shared with your team on that finding, so they’re a good place to capture why a finding was marked valid, invalid, or acknowledged.

Navigation and sharing

Keyboard shortcuts speed up review once you’re inside the panel:

Each finding has a stable URL, so you can share a direct link with teammates.

Next: Managing severity and validity