Skip to content

Vulnerability Scan Failure Slack Notify #948

Vulnerability Scan Failure Slack Notify

Vulnerability Scan Failure Slack Notify #948

Triggered via schedule July 8, 2026 16:30
Status Success
Total duration 2m 34s
Artifacts 1
vulnerability-scan-failure-notify  /  vulnerability_scan
2m 29s
vulnerability-scan-failure-notify / vulnerability_scan
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#L39
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L36
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "UID2_OPERATOR_E2E_CLIENT_API_SECRET_NON_SHARING_RECIPIENT") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L34
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "UID2_OPERATOR_E2E_CLIENT_API_SECRET_SHARING_RECIPIENT") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L17
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L36
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L35
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "UID2_OPERATOR_E2E_CLIENT_API_KEY_NON_SHARING_RECIPIENT") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L32
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L31
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L24
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L19
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/

Artifacts

Produced during runtime
Name Size Digest
IABTechLab~uid2-e2e~F1EF6C.dockerbuild
39.4 KB
sha256:aa160b57520b64e89edbbdcba1864dd8c58e71e9004c965d2de54dfa1874cb0e