govulncheck #411
Annotations
10 errors and 2 warnings
|
govulncheck
provenance.Signatory.ClearSign calls clearsign.dashEscaper.Close, which eventually calls ed448.Sign
|
|
govulncheck
provenance.Signatory.DecryptKey calls packet.PrivateKey.Decrypt, which eventually calls ed448.PrivateKey.Seed
|
|
govulncheck
provenance.Signatory.DecryptKey calls packet.PrivateKey.Decrypt, which eventually calls ed448.NewKeyFromSeed
|
|
govulncheck
provenance.init calls packet.init, which eventually calls ed25519.init
|
|
govulncheck
provenance.loadKey calls openpgp.ReadEntity, which eventually calls ed25519.Verify
|
|
govulncheck
provenance.Signatory.ClearSign calls clearsign.dashEscaper.Close, which eventually calls ed25519.Sign
|
|
govulncheck
provenance.Signatory.DecryptKey calls packet.PrivateKey.Decrypt, which eventually calls ed25519.PrivateKey.Seed
|
|
govulncheck
provenance.Signatory.DecryptKey calls packet.PrivateKey.Decrypt, which eventually calls ed25519.NewKeyFromSeed
|
|
govulncheck
provenance.init calls packet.init, which eventually calls conv.init
|
|
govulncheck
provenance.loadKey calls openpgp.ReadEntity, which eventually calls conv.BytesLe2BigInt
|
|
govulncheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1, actions/setup-go@v5.0.0. 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/
|
|
govulncheck
Failed to restore: Cache service responded with 400
|