Skip to main content

Scan History

View and manage the scan history for a specific repository.

Viewing Scan History​

The Scan History page shows all previous scans for a repository, organized by date (most recent first).

Step 1: Navigate to Scan History​

  1. Log in to your Can I Run That account at https://app.canirunthat.com
  2. Go to Dashboard and locate the repository you want to view history for
  3. Click on the repository to open the Repository Status page
  4. Click the Scan History button or link to view all previous scans for that repository

Scan History Page

Understanding the Scan History Table​

The Scan History table includes the following columns:

ColumnDescription
Scan #Sequential scan number for this repository (e.g., #1, #2, #3)
DateThe date and time the scan completed
StatusCurrent status: Completed, Running, Pending, Failed, or No Changes
ScoreThe overall risk score (0–100) — only shown for completed scans
GradeThe overall risk grade (A, B, C, D, E, F) — only shown for completed scans
ChangeHow the score changed from the previous scan (e.g., +5, -10, or "First scan")
TriggerHow the scan was triggered: Initial, Manual, or Scheduled
CommitThe Git commit SHA of the scanned code
FilesNumber of new, changed, and reused files in this scan
ActionButton to view the report (for completed scans)

Scan History Table

Scan Status Values​

  • Completed — Scan finished successfully with a report available
  • Running — Scan is currently in progress (analyzing code)
  • Pending — Scan is queued and waiting to start
  • Failed — Scan encountered an error; check repository status for details
  • No Changes — Code hadn't changed from the previous scan; no new report generated

Re-Scanning a Repository​

You can trigger a new scan at any time to analyze the latest code changes.

Step 1: Start a Re-scan​

  1. From the Scan History page, click the Re-scan Now button in the top right
  2. Alternatively, go to the Repository Status page and click Re-scan Now

Scan History Page with Re-scan Button

Step 2: Monitor the Scan​

  • A new scan will be added to the history table with "Pending" status
  • The scan will move to "Running" once it starts analyzing the code
  • The scan typically takes a few minutes to several hours, and in some cases up to 24 hours, depending on repository size and system load
  • Refresh the page to see the latest scan status

What Happens During a Scan​

  • Can I Run That clones the latest version of the repository branch
  • The code is analyzed for security vulnerabilities, dependencies, and code quality issues
  • A new report is generated when the scan completes
  • The previous scan's report remains available for comparison
info

If no code changes are detected, the scan will complete with "No Changes" status and no new report is generated.

Next Steps​