> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/github/malicious-files/scan-status.md).

# Scan status

The **Scan Status** page shows the most recent scan of each repository in the organization. Each scan checks the repository's full history, across every branch, pull request and tag, against the [malicious file rules](https://docs.stepsecurity.io/github/malicious-files/rules.md).

To open it, select **Malicious Files** > **Scan Status** in the **GitHub** section of the left navigation.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FFpW1dabrxya6PQ8xFUvz%2FScreenshot%202026-10-27%20at%2016.13.46.png?alt=media&amp;token=77eef708-669a-4657-ae8b-29282ea10104" alt=""><figcaption></figcaption></figure>

For each repository, StepSecurity shows:

* **Repository:** the repository name
* **Scan status:** the result of the most recent scan, for example `Completed`
* **Duration:** how long the scan took
* **Commits:** the number of commits scanned
* **Blobs:** the number of file versions (Git blobs) scanned
* **Repo size:** the size of the repository
* **Findings:** the number of findings in the repository
* **Last scan** and **Next scan:** when the repository was last scanned and when the next scan is scheduled

Use the search box to find a repository, the **Scan status** filter to narrow the list by status, and the **Only repositories with active findings** toggle to show only repositories that need attention.

To see the files a scan flagged, go to [Findings](https://docs.stepsecurity.io/github/malicious-files/findings.md). To see what each scan checks for, go to [Rules](https://docs.stepsecurity.io/github/malicious-files/rules.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stepsecurity.io/github/malicious-files/scan-status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
