Skip to content

Weekly Cryptographic Vulnerability Scan #20

Weekly Cryptographic Vulnerability Scan

Weekly Cryptographic Vulnerability Scan #20

Triggered via schedule March 23, 2026 09:24
Status Success
Total duration 7m 15s
Artifacts 1

weekly-scan.yml

on: schedule
Scan Go Repositories for Crypto Vulnerabilities
7m 11s
Scan Go Repositories for Crypto Vulnerabilities
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Scan Go Repositories for Crypto Vulnerabilities
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 Go Repositories for Crypto Vulnerabilities
Retention days cannot be greater than the maximum allowed retention set within the repository. Using 90 instead.
Scan Go Repositories for Crypto Vulnerabilities
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2

Artifacts

Produced during runtime
Name Size Digest
cryptoguard-scan-results Expired
9.36 KB
sha256:597be0bb3d1f4034f114d8d8a13b6c1b88ebc0242f0d25b5655cc94cbe532538