git.security.list-code-scanning-alertsCode scanning alerts on the default branch
Request syntax
GET /git/api/repositories/{repoId}/security/code-scanning-alertsPath parameters
repoIdRequiredstring
Constraints: uuid
Response
200 with the alerts: id, tool, state, ruleId, ruleDescription, severity, message, path, startLine, endLine, helpUri and the commits it was first and last seen on.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
[].idAlwaysstring
The alert[].orgIdAlwaysstring
The organization[].repoIdAlwaysstring
The repository[].toolAlwaysstring
The tool that reported it, e.g. Semgrep[].fingerprintAlwaysstring
Identifies the same finding across uploads[].stateAlwaysone of open, fixed, dismissed
fixed once an analysis of the default branch no longer reports it[].ruleIdAlwaysstring
The tool's rule id[].ruleDescriptionAlwaysstring, may be null
The rule's description; null when the tool gives none[].severityAlwaysone of critical, high, medium, low, note
The severity[].messageAlwaysstring
What the tool says about this finding[].pathAlwaysstring
The file, from the repository root[].startLineAlwaysnumber, may be null
First line of the finding; null when not given[].endLineAlwaysnumber, may be null
Last line of the finding; null when not given[].helpUriAlwaysstring, may be null
A link to the rule's documentation; null when none[].firstSeenCommitOidAlwaysstring
The commit it was first reported on[].lastSeenCommitOidAlwaysstring
The commit it was last reported on[].lastSeenRefAlwaysstring
The ref of the analysis that last saw it: the default branch or a pull request head[].dismissedReasonAlwaysstring, may be null
Why it was dismissed; null unless dismissed[].dismissedByIamUserIdAlwaysstring, may be null
Who dismissed it; null unless dismissed[].fixedAtAlwaysstring, may be null
When it was found fixed (ISO 8601); null until then[].createdAtAlwaysstring
When it was first reported (ISO 8601)[].updatedAtAlwaysstring
When the alert last changed (ISO 8601)
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 list-code-scanning-alerts repoIdcurl -X GET "https://console.platform-development.deutschecloud.app/git/api/repositories/repoId/security/code-scanning-alerts" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_security_list-code-scanning-alerts.