Skip to content
Docker Image CVE Scanner

Docker Image CVE Scanner #766

Sign in to view logs

Docker Image CVE Scanner

Docker Image CVE Scanner #766

Triggered via schedule April 19, 2026 04:30
@mimaisonmimaison
⁠ 8ae35c0
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 (3.9.2)
Process completed with exit code 1.
scan_jvm (4.0.2)
The strategy configuration was canceled because "scan_jvm._3_9_2" failed
scan_jvm (4.0.2)
Process completed with exit code 1.
scan_jvm (4.1.2)
The strategy configuration was canceled because "scan_jvm._3_9_2" failed
scan_jvm (4.1.2)
The operation was canceled.
scan_jvm (4.2.0)
The strategy configuration was canceled because "scan_jvm._3_9_2" failed
scan_jvm (4.2.0)
Process completed with exit code 1.
scan_jvm (latest)
The strategy configuration was canceled because "scan_jvm._3_9_2" failed
scan_jvm (latest)
The operation was canceled.
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 (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/
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 (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 (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/

Artifacts

Produced during runtime
Name Size Digest
scan_report_jvm_3.9.2.txt
3.41 KB
sha256:2606e02eb5d555d7f58994ea8a8e6dbfa13afa231ab67f5e65b415c76bdc5341
scan_report_jvm_4.0.2.txt
2.98 KB
sha256:3f44ecfabcfd27156313ee917f0960e3f06064327a55a447d57c273f84571e07
scan_report_jvm_4.1.2.txt
3.02 KB
sha256:89854429d272ae9a210e0ce8b4a1982e261676159ce5bdc01d9eefa02f551cd6
scan_report_jvm_4.2.0.txt
3.17 KB
sha256:45e18d970c217f5ac808c52140a02c25e9a0fb4bcf2051a5b38a11de25aa4153
scan_report_jvm_latest.txt
3.17 KB
sha256:0dbdddf87a07758e80c51345d509d3844ba67874d32ceecc216c36b372994ca1