Skip to main content

​
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

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

​
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

​
Live Scan Progress

Active scans can show live progress below the lifecycle status:
  • The current analysis phase and its position in the scan pipeline
  • A progress bar across the configured analysis phases
  • Completed and total item counts for phases that process individual findings, functions, call chains, secrets, or changes
  • Estimated time remaining when Cysmiq has at least three comparable completed scans for the same repository and scan type
Time estimates use recent comparable scan history and might not appear until enough history is available. When detailed progress is unavailable, the lifecycle status continues to show whether the scan is queued, active, recovering, or complete.

​
Drill-Down Actions

Use the row action menu to:
  • Select Rescan to retry an eligible failed scan
  • 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
Rescan appears when the repository is active, the failed scan still represents the current ref head, and another scan has not already replaced it. 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.