Skip to content
Docker Image CVE Scanner

Docker Image CVE Scanner #823

Sign in to view logs

Docker Image CVE Scanner

Docker Image CVE Scanner #823

Triggered via schedule June 15, 2026 05:13
@mimaisonmimaison
⁠ 27b8a5e
trunk
Status Failure
Total duration 50s
Artifacts 6

docker_scan.yml

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

Annotations

11 errors and 6 warnings
scan_jvm (4.1.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 (latest)
The strategy configuration was canceled because "scan_jvm._4_1_2" failed
scan_jvm (latest)
The operation was canceled.
scan_jvm (4.2.1)
The strategy configuration was canceled because "scan_jvm._4_1_2" failed
scan_jvm (4.2.1)
The operation was canceled.
scan_jvm (4.3.0)
The strategy configuration was canceled because "scan_jvm._4_1_2" failed
scan_jvm (4.3.0)
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 16th, 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 16th, 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 16th, 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.1)
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 16th, 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.3.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 16th, 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 16th, 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
4.25 KB
sha256:211a34290dc56d721fcbd5898596b983872d9ece4d835785de57a25a29390d24
scan_report_jvm_4.0.2.txt
3.53 KB
sha256:8d02d4c52f1b6016bd996c778356e779933bf9d580cdf5a1b56f1713d33e3f17
scan_report_jvm_4.1.2.txt
3.56 KB
sha256:30b6014305fa901ec5b54cca71f5274bcc0b4640665b92bf1f48b1b22442dcde
scan_report_jvm_4.2.1.txt
2.17 KB
sha256:3169dad4e02bc543d330027dcccc1a4205f289b4a076aad0ee36ddae6f97c66a
scan_report_jvm_4.3.0.txt
2.17 KB
sha256:9424015b5d36651efb8d99d81e2e2f2b2b67665a432b602ffa5642a42867f9ab
scan_report_jvm_latest.txt
3.69 KB
sha256:d49a348b31ba7fe99b4fd551f22385f589202164d674157008c202ac7ed50b60