Skip to content
Docker Image CVE Scanner

Docker Image CVE Scanner #767

Sign in to view logs

Docker Image CVE Scanner

Docker Image CVE Scanner #767

Triggered via schedule April 20, 2026 04:32
@mimaisonmimaison
⁠ 8ae35c0
trunk
Status Failure
Total duration 1m 9s
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 (4.1.2)
Process completed with exit code 1.
scan_jvm (latest)
The strategy configuration was canceled because "scan_jvm._4_1_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_1_2" failed
scan_jvm (3.9.2)
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 (4.2.0)
The strategy configuration was canceled because "scan_jvm._4_1_2" failed
scan_jvm (4.2.0)
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 (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.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.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.2.0)
No files were found with the provided path: scan_report_jvm_4.2.0.txt. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size Digest
scan_report_jvm_3.9.2.txt
3.41 KB
sha256:14a11edf20ef2156baea2b3fc765980780c6bdaa1a529ce39eebca42c887d448
scan_report_jvm_4.0.2.txt
2.98 KB
sha256:07c584c9e28b4c8da929c6c2eafa54c9356f1add03adce91eb63c5c91791f8b2
scan_report_jvm_4.1.2.txt
3.02 KB
sha256:732a86f9b7dc1fa3d3a47d5ee89ccad3cf1d507058aba5cd9b550e74e9a781d3
scan_report_jvm_latest.txt
3.17 KB
sha256:04bdec169ba96aa116ac6d52ecd3cd3b8bcec2066293ea56ae8c8a06975a7d33