git.security.scan-dependencies

Scan the default branch’s lockfiles now

POST /git/api/repositories/{repoId}/security/dependency-alerts/scanIAM git:UpdateSecurityAlertChanges state

Answers 202; the scan runs in the background and `get` shows its result.

Request syntax

POST /git/api/repositories/{repoId}/security/dependency-alerts/scan

Path parameters

  • repoIdRequired

    string

    Constraints: uuid

Response

202 with `queued`, whether a new scan job was queued. 409 while dependency alerts are off.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Fields of data

  • queuedAlways

    boolean

    Whether a new scan was queued; false when one is already waiting

Checked against the handlers: every route test validates their answers against this schema.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow git:UpdateSecurityAlert on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud git security scan-dependencies repoId

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_security_scan-dependencies.