# Scan History

The Scan History view in Xygeni provides a timeline-based breakdown of all scans performed on repositories, pipelines, or environments. It offers detailed visibility into:

* When scans occurred
* Which scans succeeded, failed or have a Warning (Warning means that at least one partial scan has an error and at least one partial scan succeeded)
* What issues or compliance results were generated

<figure><img src="https://4096647782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUTz59rJLkJBjiRWAMknU%2Fuploads%2FG1Qn8Y46UXSABavnQQtQ%2Fimage.png?alt=media&#x26;token=8949fc25-39b2-4233-b752-31fdc0f13f44" alt=""><figcaption></figcaption></figure>

### Filters & Controls

**You can filter this table by:**&#x20;

* **Status** (Success, Error or Warning)
* **Scan ID Pattern**
* **Branch Pattern**
* **Inventory** (All, Scanned, Not Scanned)
* **Issues** (Present, Not Present)
* **Compliance** (Passed, Failed)

### Scan Records Table

| Column         | Description                                              |
| -------------- | -------------------------------------------------------- |
| **Status**     | Result of the scan (`Success`, `Error`, `Warning`)       |
| **Timestamp**  | When the scan was executed                               |
| **Scan ID**    | Unique ID for audit trail                                |
| **Project**    | Target repo/project name                                 |
| **Branch**     | Branch scanned (if known)                                |
| **Inventory**  | Whether a software bill of materials (SBOM) was included |
| **Issues**     | Indicates if any findings were detected                  |
| **Compliance** | Indicates if compliance checks were passed/failed        |
| **Actions**    | "Mark as baseline" or "View details"                     |

### Scan detail

This view also provide a detail of each scan performed. This detail include a summary with all the partial scans termination, a summary of the Inventory (SBOM) of the project, a table with the counts of the issues divided by category and severity and a summary of the compliance scan.

<figure><img src="https://4096647782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUTz59rJLkJBjiRWAMknU%2Fuploads%2Fzla9s1n4ApRUR83nBj2x%2Fimage.png?alt=media&#x26;token=7c366361-212b-4624-998f-f623386d0fb3" alt="" width="563"><figcaption></figcaption></figure>