Review dependency alerts

See which locked dependencies have known vulnerabilities, scan again, and dismiss what does not apply.

Last updated 18 November 2026View as Markdown

The lockfiles and manifests on the default branch (package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lock, go.mod, go.sum, Cargo.lock, poetry.lock, Pipfile.lock, uv.lock, requirements.txt, Gemfile.lock, composer.lock, pom.xml, gradle.lockfile and others) are matched against the vulnerability database a minute after a push and once a day. Lockfiles under node_modules, vendor, third_party and fixture or testdata directories are skipped. Each finding names the package, the installed and the fixed version, the advisory and the lockfile. The examples use the repository id 5d6c2a1e-7b3f-4c8d-9e0a-1b2c3d4e5f60.

Prerequisites

  • Permission for git:ListSecurityAlerts to read alerts, and git:UpdateSecurityAlert to scan, dismiss or reopen.
  • In the Deutsche Cloud Console, also git:GetRepository to open the repository's Security section (without it the page is not found).
  • Dependency alerts are on for the repository (the default). With them off, Scan now is not shown and a scan is refused with 409 Dependency alerts are off for this repository.

Scan now

  1. In the repository, choose Security.
  2. On Overview, next to Dependency alerts, choose Scan now. The line under Dependency alerts says when the scan is running and when it ends; the findings are listed under Dependencies.

Dismiss an alert

A dismissal takes a reason (false positive, not exploitable, accepted risk, fix later, or your own words) and an optional comment, and stays through later scans until you reopen the alert.

  1. In the repository, choose Security, then Dependencies.
  2. Choose All findings, then choose the finding.
  3. Under Dismiss, choose a reason and (optional) enter a comment.
  4. Choose Dismiss. The alert leaves the list; Show … dismissed lists it again, with Reopen.

Result

An open finding the next scan no longer reports becomes fixed; one that comes back is open again.

For npm and pnpm lockfiles, Open a fix pull request on a package (or Fix all fixable) has the platform push a branch that bumps the versions and open a pull request, so CI runs; it never merges (dcloud git security fix-dependencies, which also needs git:PushRepository and git:CreatePullRequest). A second fix for a package whose fix pull request is open is refused with 409 A fix pull request is already open: #<n>. For other ecosystems, upgrade to the fixed version yourself.

Did this page help you?