[Cycode] Fix for vulnerable manifest file dependency - dompurify updated to version 3.4.6#89
Open
cycode-security[bot] wants to merge 1 commit into
Conversation
…ted to version 3.4.6
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.
Cycode Vulnerable Dependencies Update
This pull request updates the following manifest file:
ui/app/package.json📂 ui/app/package.json
1 package will be updated to resolve vulnerabilities:
dompurifyWarning
Lock file generation failed for one or more manifest files in this pull request. Please regenerate the lock file manually before merging.
Note
Low Risk
Single dependency version bump with no logic changes; verify the lockfile is regenerated and that sanitization behavior is unchanged in QA.
Overview
Bumps the
dompurifydependency inui/app/package.jsonfrom ^3.2.4 to ^3.4.6 to address a reported vulnerable dependency (Cycode).No application code changes;
DOMPurify.sanitizeusage (e.g. inConfig.tsxfor rendered frontend information markdown) stays the same. The PR notes that lock file regeneration failed and should be done manually before merge.Reviewed by Cursor Bugbot for commit 9ef7add. Bugbot is set up for automated code reviews on this repo. Configure here.