chore(deps): Bump dompurify from 3.3.1 to 3.3.2

[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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
coding-drills	Ready	Preview, Comment	Mar 28, 2026 10:36am

[entelligence-ai-pr-reviews]

---

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this is a routine patch-level dependency bump of dompurify from 3.3.1 to 3.3.2, which is a security/sanitization library where staying current is important. The changes are confined to package.json, package-lock.json, and pnpm-lock.yaml with no application logic touched. The new engines: >=20 constraint in the lockfile is worth a quick sanity check against the project's Node.js runtime version, but as a patch release this carries minimal risk. No review comments were generated and no pre-existing unresolved concerns apply to this changeset.

Key Findings:

• All changes are strictly in dependency manifest and lockfile files (package.json, package-lock.json, pnpm-lock.yaml), with zero modifications to application source code, reducing risk to near zero.
• The dompurify 3.3.1 → 3.3.2 bump is a patch release for a security-focused sanitization library; keeping it up to date is a best practice and typically fixes minor vulnerabilities or edge-case bypasses.
• The newly introduced engines: >=20 field for dompurify in the lockfile should be verified to match the project's target Node.js runtime, but this is a lockfile-level metadata annotation rather than a breaking runtime change.
• Transitive bumps to @babel/code-frame@7.29.0 and @babel/runtime@7.29.2 are standard follow-on updates with no known regressions, and the glob@11.1.0 deprecation notice is informational only and not introduced by this PR.

Files requiring special attention

• package-lock.json
• pnpm-lock.yaml