> 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/app-builder/security-scans.md).

# Security Scans

Security scans an app's dependencies for known vulnerabilities on each build, keeps the result per version, and lets you review each finding and remediate it. Open it from the app workspace's **More** menu → **Security**.

<figure><img src="/files/iiTX2FVP3ranqVmQT59j" alt="The Security screen, listing build versions with findings by severity"><figcaption><p>Security, listing scans per build version.</p></figcaption></figure>

## The scans

Each build version is listed with a **Completed** status, the **commit** it scanned, and a summary of findings by severity (for example, *High 6 · Medium 5 · Low 1*). Open a scan to see its findings in full.

## Scan details

A scan opens with a severity summary — **Critical**, **High**, **Medium**, **Low**, and **Info** with counts — plus the commit and how long the scan took. You can **Show suppressed** findings, narrow by severity, **Bulk update** findings, remediate with **Fix with AI**, or export a **Report**.

<figure><img src="/files/4S910XaILeqiViGCb2EP" alt="A security scan&#x27;s detail view, with severity summary and a list of findings"><figcaption><p>Scan details, with findings by severity.</p></figcaption></figure>

Each finding is one row showing its **severity**, a title, the scanner (**Trivy**), that it's a **Dependency** issue, the lockfile it was found in (for example, `frontend/pnpm-lock.yaml`), the package, and the advisory id (a **CVE** or **GHSA** number).

<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>

{% 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.
* Findings are dependency issues from the app's lockfiles; remediation usually means upgrading a package to a patched version.
* Scans are per build version, so you can confirm the exact version you're about to ship.

## Related

{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/c10eed6161aadb656ac4137fce98a06ced6ec452" %}
[Testing](/app-builder/testing.md)
{% endcontent-ref %}

{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/KDQL1trGEyacZ7JGRO4O" %}
[Deploy](/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 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://docs.uptiq.ai/app-builder/security-scans.md?ask=<question>&goal=<endgoal>
```

`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.