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

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
TestingDeployLast updated
Was this helpful?

