Bump dompurify to 3.4.16 - #74
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
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.
Dependency change: dompurify 3.4.15 to 3.4.16, the patch Dependabot asks for (low severity: IN_PLACE sanitising with a node-removing hook). The app uses neither, its only hook adjusts link attributes after sanitising, so this is routine hygiene. Vetted: published 2026-09-23, maintainer cure53, no install scripts, no transitive dependencies, no provenance, Socket overall 81 with supply chain 99 and vulnerability 100. Installed by Caio in his own terminal at the exact version. Lint, typecheck, 1173 unit tests, build and the dashboard e2e pass on the branch.