Skip to content
Docker Image CVE Scanner

Docker Image CVE Scanner #805

Sign in to view logs

Docker Image CVE Scanner

Docker Image CVE Scanner #805

Triggered via schedule May 28, 2026 04:54
@mimaisonmimaison
⁠ 80ee0a9
trunk
Status Failure
Total duration 53s
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.1.2)
Process completed with exit code 1.
scan_jvm (4.2.0)
Process completed with exit code 1.
scan_jvm (4.0.2)
The strategy configuration was canceled because "scan_jvm._4_1_2" failed
scan_jvm (4.0.2)
The operation was canceled.
scan_jvm (latest)
The strategy configuration was canceled because "scan_jvm._4_1_2" failed
scan_jvm (latest)
The operation was canceled.
scan_jvm (3.9.2)
The strategy configuration was canceled because "scan_jvm._4_1_2" failed
scan_jvm (3.9.2)
The operation was canceled.
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 (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/

Artifacts

Produced during runtime
Name Size Digest
scan_report_jvm_3.9.2.txt
3.98 KB
sha256:5116367ac9201841253424d44979e4abd17e1824d9301345921f2ceb9b323e92
scan_report_jvm_4.0.2.txt
3.43 KB
sha256:172920d4017728f98000959e0e4f1af8c1ad95c9945646c3aff609bd846b2b6f
scan_report_jvm_4.1.2.txt
3.47 KB
sha256:860130519c45d126ae63789c8546daffdb1a481d59171dfc67bd93c67ad60289
scan_report_jvm_4.2.0.txt
3.61 KB
sha256:309d6acbd55c4ec1d475e22d0150eb5b860c6ff043283d7486a8ca9b17fcdc63
scan_report_jvm_latest.txt
3.62 KB
sha256:48b1ef21f5840ecdff25848b3cb0f692acd84df550e2741c99cfbd7dd886573c