Skip to content
Docker Image CVE Scanner

Docker Image CVE Scanner #769

Sign in to view logs

Docker Image CVE Scanner

Docker Image CVE Scanner #769

Triggered via schedule April 22, 2026 04:28
@mimaisonmimaison
⁠ 30cea6f
trunk
Status Failure
Total duration 52s
Artifacts 5

docker_scan.yml

on: schedule
Matrix: scan_jvm
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 5 warnings
scan_jvm (4.1.2)
Process completed with exit code 1.
scan_jvm (3.9.2)
The strategy configuration was canceled because "scan_jvm._4_1_2" failed
scan_jvm (3.9.2)
Process completed with exit code 1.
scan_jvm (latest)
The strategy configuration was canceled because "scan_jvm._4_1_2" failed
scan_jvm (latest)
The operation was canceled.
scan_jvm (4.2.0)
The strategy configuration was canceled because "scan_jvm._4_1_2" failed
scan_jvm (4.2.0)
The operation was canceled.
scan_jvm (4.0.2)
The strategy configuration was canceled because "scan_jvm._4_1_2" failed
scan_jvm (4.0.2)
The operation was canceled.
scan_jvm (4.1.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
scan_jvm (3.9.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
scan_jvm (latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
scan_jvm (4.2.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
scan_jvm (4.0.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/

Artifacts

Produced during runtime
Name Size Digest
scan_report_jvm_3.9.2.txt
3.41 KB
sha256:84dad6bc6d33ca54d5cbf645cfc1dbfe07c208a155be2580b139fe7c5fb30078
scan_report_jvm_4.0.2.txt
2.98 KB
sha256:3a5e2cc228dd050bafebfd13186d03f4df7c90901e2e7266fa1098a6d7bcad45
scan_report_jvm_4.1.2.txt
3.02 KB
sha256:39bf6694478fe6edc5b02d0869afc1aa1d78af2e58f8fb15080926e4cc4ec666
scan_report_jvm_4.2.0.txt
3.17 KB
sha256:f0bb2ac8b108b127f5f493cdda99c9457ee662dd3c040ce7744822a3bbe78152
scan_report_jvm_latest.txt
3.17 KB
sha256:edd864e277497411e9890f90c46464f1ed13961accb65c3ec56e3603307fee39