chore: bump golang.org/x/crypto to fix all 13 Dependabot alerts - #31
Merged
Conversation
All open alerts (7 critical, 2 high, 4 moderate) point at golang.org/x/crypto < 0.52.0, an indirect dependency. Upgrade it to v0.54.0 (x/sys and x/text follow along). Note the vulnerable packages are not actually compiled into the binary — go mod why reports the main module does not need x/crypto — so this is hygiene rather than a live exposure.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Sixth item from the improvement backlog. All 13 open Dependabot alerts (7 critical, 2 high, 4 moderate) are advisories against a single package:
golang.org/x/crypto< 0.52.0, present as an indirect dependency at v0.48.0. The advisories are largely in its SSH implementation.go get golang.org/x/crypto@latest→ v0.54.0, comfortably past the first patched version (0.52.0).x/sysandx/textwere upgraded alongside as transitive requirements.go mod why golang.org/x/cryptoreports the main module doesn't compile any of its packages — it's only in the module graph (via sprig's crypto template funcs) — so the CLI binary was never actually exposed. The bump clears the alerts and keeps the graph clean.Test plan
go build ./... && go vet ./... && go test -race ./...passes locally after the bump;go mod tidyapplied.🤖 Generated with Claude Code