Skip to content
Docker Image CVE Scanner

Docker Image CVE Scanner #770

Sign in to view logs

Docker Image CVE Scanner

Docker Image CVE Scanner #770

Triggered via schedule April 23, 2026 04:30
@mimaisonmimaison
⁠ 3e32d9a
trunk
Status Failure
Total duration 50s
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.0.2)
Process completed with exit code 1.
scan_jvm (latest)
The strategy configuration was canceled because "scan_jvm._4_0_2" failed
scan_jvm (latest)
Process completed with exit code 1.
scan_jvm (3.9.2)
The strategy configuration was canceled because "scan_jvm._4_0_2" failed
scan_jvm (3.9.2)
The operation was canceled.
scan_jvm (4.1.2)
The strategy configuration was canceled because "scan_jvm._4_0_2" failed
scan_jvm (4.1.2)
The operation was canceled.
scan_jvm (4.2.0)
The strategy configuration was canceled because "scan_jvm._4_0_2" failed
scan_jvm (4.2.0)
Process completed with exit code 1.
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 (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 (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.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/

Artifacts

Produced during runtime
Name Size Digest
scan_report_jvm_3.9.2.txt
3.41 KB
sha256:1c603a7b6db45252204ae153ec03fd6118f5b63e10e1f19f710d8671aea065d7
scan_report_jvm_4.0.2.txt
2.98 KB
sha256:936e92ef387a12d5b06384527bca36e0ace6b85b08c92cec8ca550ff320a9125
scan_report_jvm_4.1.2.txt
3.02 KB
sha256:49eb32135e20cf3d6c31748b8ca4f7252e2f4cf44bebacd3098c4e059906fd26
scan_report_jvm_4.2.0.txt
3.17 KB
sha256:e5f8664d1977fc29d9894c2ac293823db2cfa458c38d73c44688779ef3c2e4cc
scan_report_jvm_latest.txt
3.17 KB
sha256:d3c771b587992d34da7cb8b9dfb0a10b6f2b9cc659b9983960a1d259cbf1397b