Skip to content
Docker Image CVE Scanner

Docker Image CVE Scanner #799

Sign in to view logs

Docker Image CVE Scanner

Docker Image CVE Scanner #799

Triggered via schedule May 22, 2026 04:50
@mimaisonmimaison
⁠ c5f16d2
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 (3.9.2)
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 (4.2.0)
The strategy configuration was canceled because "scan_jvm._3_9_2" failed
scan_jvm (4.2.0)
The operation was canceled.
scan_jvm (4.0.2)
The strategy configuration was canceled because "scan_jvm._3_9_2" failed
scan_jvm (4.0.2)
The operation was canceled.
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 (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/
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/

Artifacts

Produced during runtime
Name Size Digest
scan_report_jvm_3.9.2.txt
3.98 KB
sha256:8f14d45ab14a72ef9f6eb9a6513bdf9f570b9960a913b27c6207b44f3fe26c82
scan_report_jvm_4.0.2.txt
3.43 KB
sha256:474ae9a25e58cdc8d125700ca97e8a1c5c509b1b7107cb1fdeff029d3179f65f
scan_report_jvm_4.1.2.txt
3.47 KB
sha256:3c57c7eb46fc6a06e7a24f5320a0d4051f6a89a9c7afa4f244e00c0e556ac7d2
scan_report_jvm_4.2.0.txt
3.61 KB
sha256:c925f3db5e32aa4283e601aea49747d491979ffefac6bf31e49cf873d91e9c47
scan_report_jvm_latest.txt
3.62 KB
sha256:621430b1fb154dd3273534c4484a664f38cc47b8687b2c3023445e9fa672ab74