fix(security): resolve uuid vulnerability alert (GHSA-w5hq-g745-h8pq) - #86
Merged
Conversation
…q-g745-h8pq @lhci/cli (still at its latest release, 0.15.1) pins uuid ^8.3.1, which carries a missing-bounds-check vulnerability in v3/v5/v6. uuid is dev-only tooling here (Lighthouse CI), so overriding it to the patched line is safe.
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
uuid< 11.1.1, missing buffer bounds check in v3/v5/v6)@lhci/cli— even at its latest release, 0.15.1 — still pinsuuid: ^8.3.1, so the fix requires anoverridesentry rather than a dependency bumpuuidis dev-only tooling here (used transitively by Lighthouse CI), so forcing it to 11.1.1 carries no runtime riskTest plan
npm run typechecknpm run lintnpm run test(273 tests, all passing)package-lock.jsonresolvesuuidto11.1.1🤖 Generated with Claude Code