Scans

The /scans page is the organization-wide record of every scan that has run — across all projects, branches, and trigger sources.

The scans table

Each row is one scan run:

• Scan ID — opens Scan Detail.
• Project and branch the scan ran against.
• Trigger — ci (CLI / pipeline), manual, or an SCM webhook (push / pull request).
• Scan types — which engines ran.
• Findings — the count produced.
• Duration and created time.
• Status — see the lifecycle below.

Filters

Filter	Effect
Search	Match by scan ID.
Status	queued / running / completed / failed / cancelled.
Scan type	SAST, SCA, Secrets, IaC, Malware, or Container.
Project	Limit to one project.
Trigger	ci versus manual.

Activity chart

Above the table, a chart plots scan volume over the recent window, honoring the active filters — a quick read on how busy your scanning has been.

Scan status lifecycle

Status	Meaning
queued	Accepted, waiting for a worker.
running	Engines are executing.
completed	Finished; findings are available.
failed	An engine or the run errored — results may be partial or absent.
cancelled	Stopped before completion.

Exporting

Export CSV downloads the scans currently matching your filters. See Exports for the column schema.

Scans page vs. scan engines

This page is the history of scan runs. For what each engine detects and how to tune it, see Scan Engines.

Where to go next

Scan Detail Findings and dependencies from one run.

Scan Engines SAST, SCA, Secrets, IaC, Malware, Container.