Skip to content

fix(analyzer): improvement to dockerfile scanning #6580

fix(analyzer): improvement to dockerfile scanning

fix(analyzer): improvement to dockerfile scanning #6580

Triggered via pull request April 13, 2026 17:28
Status Success
Total duration 16m 15s
Artifacts 4

go-e2e-debian.yaml

on: pull_request
Matrix: e2e-tests
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
e2e-tests-debian-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@5a3ec84eff668545956fd18022155c47e93e2684, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile.debian#L63
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: docker/Dockerfile.debian#L48
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/
The 'as' keyword should match the case of the 'from' keyword: docker/Dockerfile.debian#L6
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
e2e-tests-debian-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@5a3ec84eff668545956fd18022155c47e93e2684, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, docker/setup-buildx-action@e468171a9de216ec08956ac3ada2f0791b6bd435, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile.debian#L63
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: docker/Dockerfile.debian#L48
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/
The 'as' keyword should match the case of the 'from' keyword: docker/Dockerfile.debian#L6
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/

Artifacts

Produced during runtime
Name Size Digest
Checkmarx~kics~KI0LON.dockerbuild
102 KB
sha256:70dd1f1aad5580a1da236629802f1a42531a2a0586a66ea7dc307487f1649d98
Checkmarx~kics~YJ2MS6.dockerbuild
106 KB
sha256:0b39603ca997dea1132cc61f8cacf85509a01d42b81df23bfcfb3fa4e6bee54f
e2e-tests-report-debian-amd64
4.85 KB
sha256:f730980e4922b7389ae6602f3d474b16ce149e963de3f574c0bd6578929e43e1
e2e-tests-report-debian-arm64
4.84 KB
sha256:4146218937a48ea10d696696e24453a4e5187e7d53ec2994c5be1e678d807dbe