Skip to content

fix: zero sensitive byte slices after use across all store backends #224

fix: zero sensitive byte slices after use across all store backends

fix: zero sensitive byte slices after use across all store backends #224

Triggered via pull request March 17, 2026 15:01
@BenehikoBenehiko
synchronize #492
zero/out
Status Success
Total duration 46s
Artifacts

gomodguard.yml

on: pull_request
Check for allowed dependencies per module
41s
Check for allowed dependencies per module
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Check for allowed dependencies per module
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@c94ce9fb468520275223c153574b00df6fe4bcc9, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
Check for allowed dependencies per module
Input 'install' has been deprecated with message: "docker buildx install" command is deprecated and will be removed in a future release, use BUILDX_BUILDER environment variable instead
Check for allowed dependencies per module
Input 'install' has been deprecated with message: "docker buildx install" command is deprecated and will be removed in a future release, use BUILDX_BUILDER environment variable instead