Open
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
1 participant
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
Why
The open alerts were coming from the Excalidraw dependency chain in the draw UI package. The existing `0.18.0` package pulled in vulnerable Mermaid, DOMPurify, and NanoID versions. Targeted overrides either left vulnerable subtrees behind or introduced newer advisory chains, so the most stable fix was to move to the first non-vulnerable Excalidraw release path and align React to that package's supported peers.
Impact
This keeps the draw UI buildable while clearing the vulnerable dependency graph that Dependabot was flagging. The change is isolated to the draw UI package and its lockfile.
Validation