> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/console/app-builder/security-scans.md).

# Security Scans

Find, review, and remediate vulnerabilities and exposed secrets in each app build.

Security runs dependency, secret and static-analysis scans on every saved app version, with the scanners **Trivy**, **Semgrep** and **Gitleaks**. It keeps the result per version, and lets you review each finding and remediate it. Open it from the app workspace's **More** menu → **Security**.

## The scans

Scans are listed in a table, one row per build version. The columns are **Version** (for example, *Version 2.0.0*), **Status**, the number of findings at each severity (**Critical**, **High**, **Medium**, **Low** and **Info**), and **Started**. A scan that is still running shows a spinner in **Status**, and the table refreshes until it finishes. Select a row, or **View** in its row menu, to open the scan.

## Scan details

A scan opens with its **Status**, **Commit**, **Started**, **Duration**, the number of **Findings** and its **Scanners**, for example *3/3 passed*. Select the scanners value to list each tool, such as **Trivy**, **Semgrep** and **Gitleaks**, as **Completed**, **Failed** or **Skipped**, with the error for a failed one. Use **Bulk update** to mark findings together, **Fix with AI** to remediate, or **Report** to download a report.

Findings are listed in a table with **Severity**, **Finding**, **Location** (for example, the lockfile it was found in), **Tool** and **Status** (**Should fix** or **Won't fix**). Two filters narrow the list: **Severity**, which shows **All severities** by default, and **Suppressed**, which shows suppressed findings by default; choose **Hide** to remove them. A finding marked **Won't fix** is suppressed.

Select a row, or **View** in its row menu, to open the finding in a dialog. The dialog shows its **Severity**, **Status**, **Tool**, **Category**, **Location**, **Package**, the advisory id (a **CVE**, for a dependency), a **Description** and a **Remediation**. The row menu offers the other status: **Mark as Won't fix** on a Should fix finding, and **Mark as Should fix** on a Won't fix one.

<details>

<summary>Details</summary>

Read the finding's description, any available patches, and a **Remediation** — for example, *Upgrade fast-uri to 2.4.3, 3.1.4, 4.1.1 or later*.

</details>

While **Fix with AI** is working, the button is greyed out. Its fix arrives as a new version — for example, *Version 2.0.0 (Latest): Fix the actionable security issues detected by security scan…* in the version selector.

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-2e08cf92fd58dd80656fb43669717f08b456abf4%2Fqore_app-builder_how-to-version-selector_rounded_shadow.png?alt=media" alt="The version selector open beside the Security scans list, with Version 2.0.0 (Latest), Fix the actionable security issues detected by security scan, above Version 1.0.0"><figcaption><p>A Fix with AI remediation, as a new version.</p></figcaption></figure>

{% hint style="warning" %}
**Fix with AI** changes the app to remediate a finding — it edits the app's dependencies through the build agent, not just the report. Review the change it makes, and re-check the tests and scan afterward.
{% endhint %}

## Why this matters

* Security tells you what vulnerabilities a build carries before you publish it.
* A dependency finding comes from the app's lockfiles, and remediation usually means upgrading a package to a patched version. Secret and static-analysis findings come from Gitleaks and Semgrep.
* Scans are per build version, so you can confirm the exact version you're about to ship.

## Related

{% content-ref url="/pages/c10eed6161aadb656ac4137fce98a06ced6ec452" %}
[Testing](https://docs.uptiq.ai/ai-workbench-qore/console/app-builder/testing.md)
{% endcontent-ref %}

{% content-ref url="/pages/KDQL1trGEyacZ7JGRO4O" %}
[Deploy](https://docs.uptiq.ai/ai-workbench-qore/console/app-builder/deploy.md)
{% endcontent-ref %}


---

# 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.uptiq.ai/ai-workbench-qore/console/app-builder/security-scans.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.
