Skip to content
Docker Image CVE Scanner

Docker Image CVE Scanner #760

Sign in to view logs

Docker Image CVE Scanner

Docker Image CVE Scanner #760

Triggered via schedule April 13, 2026 04:32
@mimaisonmimaison
⁠ acd37fc
trunk
Status Failure
Total duration 47s
Artifacts 5

docker_scan.yml

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

Annotations

8 errors and 5 warnings
scan_jvm (4.2.0)
Process completed with exit code 1.
scan_jvm (3.9.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 (latest)
The strategy configuration was canceled because "scan_jvm._3_9_2" failed
scan_jvm (latest)
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.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.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 (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.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.12 KB
sha256:67f6a31bd432d95ff6c86f582ecce3200f4bea9b22dee9bb5119322cdb170739
scan_report_jvm_4.0.2.txt
2.44 KB
sha256:521b181bd2f4d326bef4711b9f17f3236c0bc30901effa0cac36d4dac91dd819
scan_report_jvm_4.1.2.txt
2.79 KB
sha256:7936438f7a3c1b574f6cad175cb25135caeaa2f8e114eb004890b283e65fe7fe
scan_report_jvm_4.2.0.txt
2.94 KB
sha256:7636142bd0ee28fea81bacd1298da9d3c771f5b10d8671de2980622f31f3f420
scan_report_jvm_latest.txt
2.95 KB
sha256:97c26232d8fa4f5d3e6e1663b383c56f430405d02982cc262984731fc6a495ed