Skip to content
Docker Image CVE Scanner

Docker Image CVE Scanner #780

Sign in to view logs

Docker Image CVE Scanner

Docker Image CVE Scanner #780

Triggered via schedule May 3, 2026 04:43
@mimaisonmimaison
⁠ 162b3a1
trunk
Status Failure
Total duration 1m 1s
Artifacts 4

docker_scan.yml

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

Annotations

9 errors and 6 warnings
scan_jvm (latest)
Process completed with exit code 1.
scan_jvm (4.2.0)
The strategy configuration was canceled because "scan_jvm.latest" failed
scan_jvm (4.2.0)
Process completed with exit code 1.
scan_jvm (3.9.2)
The strategy configuration was canceled because "scan_jvm.latest" failed
scan_jvm (3.9.2)
The operation was canceled.
scan_jvm (4.0.2)
The strategy configuration was canceled because "scan_jvm.latest" failed
scan_jvm (4.0.2)
The operation was canceled.
scan_jvm (4.1.2)
The strategy configuration was canceled because "scan_jvm.latest" failed
scan_jvm (4.1.2)
The operation was canceled.
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 (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.1.2)
No files were found with the provided path: scan_report_jvm_4.1.2.txt. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size Digest
scan_report_jvm_3.9.2.txt
3.77 KB
sha256:9cced07f4abf8e842ec2529674ec79469d72c4540197e357ba68290e22c1701e
scan_report_jvm_4.0.2.txt
3.37 KB
sha256:59f3c1792d0870def1de0ccf6658e9ca157a2c8c71cdeca5ca792ad2273dc0fd
scan_report_jvm_4.2.0.txt
3.52 KB
sha256:2e2459eb21da2a892d977f6acc0d32978c0c51d05702f78ee7d1c12c8a4829dd
scan_report_jvm_latest.txt
3.53 KB
sha256:bfbc97d44de4d3c553ecd4e566b3002e4d2e8fda7fed279bf88ed4b378032cd2