git.security.overview

Open alerts and protection settings for every repository you may see

GET /git/api/security/overviewIAM git:ListSecurityAlertsRead

Request syntax

GET /git/api/security/overview

Response

200 with one row per repository: repoId, name, visibility, isArchived, secretPushProtection, dependencyAlerts and the open alert counts (as in `get`).

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

Fields of data

  • [].​repoIdAlways

    string

    The repository
  • [].​nameAlways

    string

    Its name
  • [].​visibilityAlways

    one of private, internal, public

    Who can see it
  • [].​isArchivedAlways

    boolean

    Archived: read-only
  • [].​secretPushProtectionAlways

    boolean

    Pushes that add a known credential format are refused
  • [].​dependencyAlertsAlways

    boolean

    The default branch's lockfiles are checked against the vulnerability database
  • [].​secretsBypassedAlways

    number

    Secrets pushed past protection and not yet resolved
  • [].​secretsBlocked30dAlways

    number

    Pushes refused for a secret in the last 30 days
  • [].​dependencyCriticalAlways

    number

    Open dependency alerts of critical severity
  • [].​dependencyHighAlways

    number

    Open dependency alerts of high severity
  • [].​dependencyOtherAlways

    number

    Open dependency alerts of medium, low or unknown severity
  • [].​codeScanOpenAlways

    number

    Open code scanning alerts on the default branch

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:ListSecurityAlerts 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 overview

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