> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/pr-and-release-gating/aikido-ci-gating-functionality/ci-scan-history-overview.md).
# CI Scan History Overview
The CI Scan History feature in Aikido provides a detailed overview of all past CI scans, offering insights into their status, newly introduced issues, and resolved issues. This is important to keep an overview of all executed scans and allow you to quickly check the diff page from previous executed scans.
### How to check your CI Scan History
**Step 1.** Go to the CI section on the [Integrations page](https://app.aikido.dev/settings/integrations) and enter the [GitHub](https://app.aikido.dev/settings/integrations/github/checks)/[Azure](https://app.aikido.dev/settings/integrations/azure-devops/checks) CI dashboard **OR** - if you are running your CI via code - go to the [CI Settings Page](https://app.aikido.dev/settings/integrations/continuous-integration).
**Step 2.** Click on "CI Scan History" located at the top right of the page.
**Step 3.** Review the overview page to see all previous CI scans, including their status, newly introduced issues, and resolved issues.
**Step 4.** Click one of the PRs to get a full overview of the executed scan.
### Filter by scan date
You can filter the CI scan history to a specific date by adding a `scan_date` query parameter to the URL:
```
https://app.aikido.dev/settings/integrations/ci/checks/scans?scan_date=2026-05-10
```
Use the `YYYY-MM-DD` format. This is handy when you need to pull up scans from a particular day during an audit or compliance review — for example, to show what ran on a specific release date or during a past incident.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.aikido.dev/pr-and-release-gating/aikido-ci-gating-functionality/ci-scan-history-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.