AI Detection

Scan history

View and manage past repository scans and their results.

Overview

The scan history page maintains a complete record of all repository scans performed by your organization. Each scan record is preserved indefinitely for audit purposes, providing a defensible trail of AI governance activities.

History table

The history table displays all scans with the following information:

  • Repository: Owner and name of the scanned repository
  • Status: Current state — Completed, Failed, Cancelled, or Scanning
  • Findings: Total number of detections including libraries, API calls, secrets, and security issues
  • Files scanned: Total source files analyzed
  • Duration: Time taken to complete the scan
  • Date: When the scan was performed

Click any completed scan row to view its full results, including library findings, API calls, detected secrets, and security vulnerabilities.

Scan history table showing past repository scans with status and findings
Complete scan history with repository, status, findings, and duration

Scan status

Each scan has one of the following statuses:

Completed

Scan finished successfully. Results are available for review.

Scanning

Scan is currently in progress.

Failed

Scan encountered an error. Check error message for details.

Managing scan history

You can delete individual scan records by clicking the trash icon in the actions column. Deletion is permanent and removes all associated findings. Consider exporting or documenting important results before deletion.

Audit trail
For compliance purposes, maintain scan history as evidence of ongoing AI governance activities. Regular scanning demonstrates due diligence in monitoring AI usage.

Filtering and pagination

Use the status filter to show only scans with a specific status (Completed, Failed, etc.). The table supports pagination for organizations with extensive scan history.

Rescanning repositories

To rescan a previously analyzed repository, navigate to the scan details page and click Rescan. This creates a new scan record while preserving the original for comparison. Alternatively, start a new scan from the Scan page with the same repository URL.

Regular rescanning helps identify newly added AI dependencies. Consider establishing a scanning schedule for critical repositories.
PreviousScanning repositories
Scan history - AI Detection - VerifyWise User Guide