> ## Documentation Index > Fetch the complete documentation index at: https://docs.cysmiq.com/llms.txt > Use this file to discover all available pages before exploring further. # Scan List View > Review scan runs, statuses, filters, and related findings from the Scans view. ## Overview Use the **Scans** view to review scan runs for repositories you can access. The table defaults to newest scans first and updates scan rows when Cysmiq receives scan status events. Each row represents one scan run tied to an asset, ref, commit SHA, scan type, trigger, lifecycle status, and result. When available, the scan title comes from the commit message, pull request title, or ref name. ## Columns | Column | What it shows | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Scan** | Commit message, pull request title, or ref name, plus the short commit SHA and pull request number when available. Commit and pull request values link to the source control provider when Cysmiq can build the provider URL. | | **Asset** | Repository name, including the organization name when available. | | **Triggered By** | The matched Cysmiq user when the VCS identity is linked, otherwise the push sender. System-triggered scans show **System**. | | **Vulnerabilities** | Badges for vulnerabilities fixed by this scan, actionable vulnerabilities first seen in this scan, inferred active vulnerabilities carried forward into this scan, and actionable policy violations when policies are enabled. Badge links open filtered vulnerability or policy violation views. | | **Status** | Current scan lifecycle status. Finished scans show runtime on hover. | | **Result** | VCS or pull request result for the scan. The badge can reflect a current PR evaluation, provider check, or scan status fallback. | | **Finished** | Relative finished time with the exact timestamp available from the date tooltip. | | **Actions** | Opens scan drill-down actions. | When one scan SHA is associated with more than one current pull request, the **Scan** column can show the number of pull requests sharing that scan. The **Result** column can summarize multiple current PR evaluations and show the first few contributing PRs. ## Filters | Filter | Matching behavior | | ---------------- | -------------------------------------------------------------------------------------------- | | **Organization** | Matches scans for accessible repositories in selected organizations. | | **Asset** | Matches selected scanned assets for repositories you can access. | | **SHA** | Searches by partial commit SHA. | | **Scan ID** | Matches the exact scan ID. Drill-down links and export links can apply this filter directly. | | **Pull Request** | Searches pull request title or pull request number. A leading `#` is optional for numbers. | | **Type** | Matches scan types present in the workspace data. | | **Status** | Matches one or more scan status labels. | ## Status and Result Labels The **Status** filter uses these public scan status labels: * **Queued** * **In Progress** * **Processing** * **Finalizing** * **Completed** * **Completed with Errors** * **Failed** * **Skipped** * **Aborted** * **Cancelled - No SWUs** * **Recovering** The **Result** column is separate from the lifecycle **Status** column. It summarizes the VCS or pull request outcome when that data is available. Result labels can include: * **PR passed**, **PR failed**, **PR unavailable**, **PR neutral**, or **PR pending** for current pull request evaluations * **PRs passed**, **PRs failed**, **PRs unavailable**, **PRs neutral**, or **PRs pending** when multiple current PR evaluations share the scan SHA * **Check passed**, **Check failed**, **Check neutral**, or **Check pending** for provider check results * **Scan passed**, **Scan failed**, **Scan neutral**, or **Scan pending** when no PR evaluation or provider check outcome is available ## Drill-Down Actions Use the row action menu to: * Open **View vulnerabilities** for vulnerabilities associated with the scan * Open **View policy violations** for policy violations associated with the scan when policies are enabled * Copy the scan ID The vulnerability badges also link to filtered views: * Fixed vulnerabilities link to vulnerabilities resolved by the scan * Actionable vulnerabilities link to vulnerabilities first seen in the scan * Inferred vulnerabilities link to active vulnerabilities carried forward into the scan * Policy violation counts link to open and pending review policy violations for the scan ## Export Select one or more scan rows and choose **Export** to export the selected scans. Exports are limited to scans you can access. Small exports download an XLSX file immediately. Larger exports are queued, and Cysmiq notifies you when the file is ready. The export includes scan identity, repository, organization, provider, ref, type, status, commit SHA, title, pull request number, trigger identity, timestamps, duration, fixed vulnerability counts, fixed-in-reference counts, actionable vulnerability counts, policy violation counts, and a link back to the scan list filtered by scan ID. ## Related Docs * [Scans](/concepts/scans) * [Filtering](/views-automation/filtering) * [Managing columns](/views-automation/managing-columns) * [Vulnerability list view](/vulnerability-management/vulnerability-list-view) * [Policy violations](/policies/violations)