Understanding results

The five result states, what coverage means, and why zero findings is not always all clear.

The result statesPermalink to The result states

When a scan reaches a terminal state, the console shows one headline. Each one means something specific, and they are deliberately not interchangeable.

Where this happens in the console

Scan historyOpen any scan to read its result.

Headline	What it means	Is your code cleared?
No issues found	The scan completed, coverage was adequate, and nothing was found.	Yes, for what this scan covers
N findings	The scan completed and reported findings for you to review.	No — review the findings
Completed · limited coverage	The scan finished but could not examine enough of the repository to vouch for the result.	No — coverage was not adequate
Results require internal review	The results need review before they can be shown.	Not yet — no result is displayed
Scan failed safely	The scan stopped without producing a result.	No — nothing was assessed
Scan canceled	The scan was cancelled before it produced a result.	No — nothing was assessed

Terminal result states as the console presents them.

What coverage meansPermalink to What coverage means

Coverage records how much of the repository the scan was actually able to examine. It is reported alongside the findings count, and it is what separates a genuine all-clear from a scan that simply did not look at very much.

Limited coverage is never an all-clear

A scan that reports zero findings with limited coverage has not cleared your repository. The console shows Completed · limited coverage instead of No issues found, and it does so precisely so that the absence of findings is not mistaken for the absence of problems.

If you see limited coverage, treat the scan as incomplete. Re-running it is usually the right next step; if it recurs on the same repository, raise it with support.

Why a scan ends without a full resultPermalink to Why a scan ends without a full result

Every result carries a category that explains how it ended. These are the categories you can see.

Category	Message you will see
Succeeded	Scan completed.
Completed with limited coverage	Scan completed with limited coverage.
Configuration error	Scan could not be started. Please try again or contact support.
Repository access error	We couldn't access the repository. Check the connection and try again.
Cancelled	Scan was canceled.
Internal error or timeout	Scan took longer than expected and stopped safely.

Result categories and their meanings.

When a result is not ready yetPermalink to When a result is not ready yet

A scan can finish a moment before its result is available. The console says the results are being prepared and keeps checking for a short window.

If the result still does not arrive after that window, the console stops waiting and tells you so rather than showing a spinner indefinitely. That state is worth reporting to support.

Exporting a resultPermalink to Exporting a result

Every result can be exported from the buttons at the top of the result view, in two formats. Both are produced in your browser from the result already on screen, so an export can never contain anything the page could not show you.

Format	Contains	Use it for
JSON	The complete result: status, coverage, the summary counts, the error category if there was one, and every finding with its full detail.	Feeding another system, or keeping a faithful record.
CSV	One row per finding, with severity, proof state, file, line, CWE, CVSS score and the remediation summary.	Opening in a spreadsheet, or pasting rows into a tracker.

The two export formats.

An exported file carries its own coverage verdict

A file outlives the screen it came from — it gets attached to a ticket or forwarded to someone who never saw the scan. So the coverage verdict travels with it: it is in the filename, in the JSON, and on every row of the CSV. A limited-coverage export says in words that it is not a clean result, and an export from a scan that failed says that no result was produced. Nothing that leaves the console can be read as an all-clear unless it genuinely is one.

A zero-finding export still has a row

An empty findings file is exactly what a clean report looks like to whoever opens it. So an export with no findings carries a single row stating what actually happened instead of being empty — which matters most when the reason for the empty list is that coverage was limited.

Where to find it

Scan historyOpen any scan and export its result from the buttons beside New scan.