fix(reachy): update vulnerable Transformers dependency - #77
Merged
Merged
Conversation
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
transformers>=5.17,<6, the scanner-recommended fixed releaseuv.lock, updating Transformers to 5.17.0 and its Tokenizers dependency to 0.23.2golang.org/x/cryptofinding against the compiled import graph and the Go vulnerability databaseGo finding assessment
The CSV provides no fixed release for
golang.org/x/crypto. The applicable module-level advisory is GO-2026-5932 for the unmaintainedgolang.org/x/crypto/openpgppackage. The exporter does not importopenpgp; its compiled dependency graph useschacha20poly1305,cryptobyte, andhkdf.govulncheck -show verbose ./...reports that the exporter is affected by 0 vulnerabilities, with GO-2026-5932 present only at module level and not in imported packages or symbols. No Go dependency change is necessary.Validation
uv lock --checkruff check .python -m compileall src testspytest -q tests/vision/test_processors.py(30 passed)govulncheck -show verbose ./...(0 reachable vulnerabilities)go mod verifygo vet ./...go test -race ./...go build ./cmd/...The full Reachy
uv run pytest -qanduv run ty checkworkflows require the project-supported macOS environment; this Linux host cannot sync the Darwin-only lock environment. The directly affected vision suite, lock validation, lint, and compilation checks pass.