build(deps): bump dompurify from 3.3.1 to 3.3.2 in /frontend

[dependabot]

Bumps dompurify from 3.3.1 to 3.3.2.

Release notes

Sourced from dompurify's releases.

DOMPurify 3.3.2

• Fixed a possible bypass caused by jsdom's faulty raw-text tag parsing, thanks multiple reporters
• Fixed a prototype pollution issue when working with custom elements, thanks @​christos-eth
• Fixed a lenient config parsing in _isValidAttribute, thanks @​christos-eth
• Bumped and removed several dependencies, thanks @​Rotzbua
• Fixed the test suite after bumping dependencies, thanks @​Rotzbua

Commits

• 5e56114 Getting 3.x branch ready for 3.3.2 release (#1208)
• e8c95f4 fix: Fixed the broken package-lock.json
• 9636037 Update package-lock.json
• 5cad4ce Getting 3.x branch ready for 3.3.2 releas (#1205)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Greptile Summary

This PR bumps dompurify from 3.3.1 to 3.3.2 in the frontend, a security-oriented patch release.

Key changes:

• package.json: version constraint updated from ^3.3.1 to ^3.3.2
• package-lock.json: resolved URL, integrity hash updated; a new engines: { node: \">=20\" } constraint is added by the upstream package

Security fixes included in 3.3.2 (from release notes):

• Fixed a possible bypass caused by jsdom's faulty raw-text tag parsing
• Fixed a prototype pollution issue when working with custom elements
• Fixed lenient config parsing in _isValidAttribute

Compatibility: The new node >= 20 engine requirement introduced by dompurify 3.3.2 is satisfied — the project's frontend/.nvmrc pins Node.js to v22.17.0.

Confidence Score: 5/5

Safe to merge — this is a pure security patch with no API changes and all compatibility requirements are met.

No logic changes — only version numbers and integrity hashes updated. The new node >= 20 engine constraint is satisfied by the project's pinned Node.js v22.17.0. The patch addresses real security issues (prototype pollution, XSS bypass), making this a beneficial and low-risk update.

No files require special attention.

Important Files Changed

Filename	Overview
frontend/package.json	Bumps dompurify dependency constraint from ^3.3.1 to ^3.3.2 — straightforward patch version update
frontend/package-lock.json	Lock file updated with new dompurify 3.3.2 resolved URL, integrity hash, and a new engines constraint (node >= 20); project's .nvmrc specifies v22.17.0 so the constraint is satisfied

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["dependabot detects dompurify 3.3.2"] --> B["package.json\n^3.3.1 → ^3.3.2"]
    B --> C["package-lock.json\nversion / hash / engines updated"]
    C --> D{"Node.js engine check\nrequires >= 20"}
    D -->|".nvmrc = v22.17.0 ✅"| E["Compatible"]
    E --> F["Security fixes applied\n• jsdom raw-text bypass\n• Prototype pollution\n• Lenient _isValidAttribute parsing"]

Loading

_{Reviews (1): Last reviewed commit: "build(deps): bump dompurify from 3.3.1 t..." | Re-trigger Greptile}