chore(deps): bump dompurify from 3.4.0 to 3.4.11

[dependabot]

Bumps dompurify from 3.4.0 to 3.4.11.

Release notes

Sourced from dompurify's releases.

DOMPurify 3.4.11

• Fixed an issue with a leaky config for hooks via setConfig, thanks @​trace37labs
• Bumped vulnerable development dependencies to arrive at plain 0 with npm audit
• Updated the osv-scanner suppression list as no vulnerable dependencies are left for now
• Updated up the linting tool-chain and removed now-redundant lint directives
• Updated the documentation is several spots, README, wiki, etc.
• Bumped several dependencies where possible

DOMPurify 3.4.10

• Refactored codebase for clarity: extracted the public type declarations into types.ts
• Decomposed the three largest sanitizer functions into focused helpers
• Removed duplicated defaults and dead branches, consolidated SAFE_FOR_TEMPLATES scrubbing into single shared path
• Improved per-node performance by hoisting the mXSS probe regexes and testing textContent before innerHTML
• Added a deterministic micro-benchmark harness (npm run bench) with a --compare mode
• Reduced CI cost by running the full three-engine browser suite once per PR
• Refreshed the demos/ folder so every demo runs again, and added a SVG-via-<img> demo
• Documented the bench and test:happydom scripts in the README
• Completed the Attack Classes & Bypass History wiki page
• Bumped several dependencies where possible

DOMPurify 3.4.9

• Further improved the handling of Trusted Types config options, thanks @​offset
• Further improved the handling of IN_PLACE sanitization, thanks @​mozfreddyb
• Added more test coverage for IN_PLACE and Trusted Types related usage
• Bumped several dependencies where possible
• Updated README and wiki with more accurate documentation & attack samples

DOMPurify 3.4.8

• Cleaned up the repository root, renamed some and removed unneeded files
• Fixed an issue with handling of Trusted Types policies, thanks @​fulstadev
• Fixed the node iterator for better template scrubbing, thanks @​IamLeandrooooo
• Included formerly missing LICENSE-MPL in published npm package, thanks @​asamuzaK
• Bumped several dependencies where possible

DOMPurify 3.4.7

• Hardened the handling of Shadow Roots when using IN_PLACE, thanks @​GameZoneHacker
• Removed a problem leading to permanent hook pollution, thanks @​offset
• Refactored the test suite and expanded test coverage significantly

DOMPurify 3.4.6

• Fixed several issues with DOM Clobbering in IN_PLACE mode, thanks @​offset & @​Bankde
• Hardened the checks for cross-realm IN_PLACE and Shadow DOM sanitization, thanks @​offset & @​Bankde
• Added more test coverage for IN_PLACE and general DOM Clobbering attacks
• Bumped several dependencies where possible

DOMPurify 3.4.5

• Fixed a bypass caused by the new HTML element selectedcontent added in 3.4.4, thanks @​KabirAcharya

Note that this is a security release for an issue introduced in 3.4.4 and should be upgraded to immediately.

... (truncated)

Commits

• 0cae518 release: 3.4.11 (#1494)
• 6ee5716 release: 3.4.10 (#1478)
• 5210247 release: 3.4.9 (#1459)
• bcdd828 release: 3.4.8 (#1439)
• ca30f07 release: 3.4.7 (#1414)
• bb7739e release: 3.4.6 (#1394)
• 011b0c7 release: 3.4.5 (#1382)
• 5817ad9 release: 3.4.4 (#1374)
• 520edb0 release: 3.4.3 (#1352)
• 6f67fd3 Sync/3.4.2 (#1322)
• Additional commits viewable in compare view

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.

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.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[github-actions]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: chore(deps): bump dompurify from 3.4.0 to 3.4.11
• Issue: None — this is a clear, high-quality dependency update title.
• Recommendation: No change needed.

---

✅ Commit Type

• Properly selected as a dependency maintenance change (chore).
• Only one commit type is implied by the title/body, which is correct.

---

⚠️ Risk Level

• The PR body appears to be missing a checked risk selection, and the repo labels do not include a risk:low, risk:medium, or risk:high label. Based on the diff, this should be treated as medium risk because dompurify is a security-relevant dependency update and the lockfile shows broader dependency churn.
• Recommendation: Add/select the appropriate risk label and ensure the PR body matches it. If you intended a lower risk, justify why the dependency upgrade is isolated and low impact.

---

❌ What & Why

• Current: (Missing)
• Issue: This section is required by the template and should briefly explain the purpose of the dependency bump and why it is being made.
• Recommendation: Add a concise summary such as: Upgrade dompurify to 3.4.11 to pick up security fixes and dependency updates.

---

❌ Impact of Change

• This section is missing and should describe who is affected.
• Recommendation:
  • Users: Note whether sanitization behavior changes are expected or whether the update is transparent to users.
  • Developers: Mention the dependency bump and any follow-up validation needed.
  • System: Call out that this is a security-focused package update and may affect sanitization/HTML handling.

---

⚠️ Test Plan

• No test checkboxes are marked in the PR body. The diff is a dependency update only, but it is not docs-only or pure config-only: it changes runtime dependencies plus the lockfile. Since neither unit nor E2E tests are present in the diff, you should add at least one test reference or a manual-testing explanation.
• Recommendation: Check Manual testing completed and briefly state what was verified, or add an automated test if one exists for sanitizer behavior. If you rely on no-code-change validation, explain why that is sufficient.

---

✅ Contributors

• Blank is acceptable; no required action.

---

✅ Screenshots/Videos

• Not required for this dependency update.

---

Summary Table

Section	Status	Recommendation
Title	✅
Commit Type	✅
Risk Level	⚠️	Select/add the matching risk label and body value
What & Why	❌	Add a brief explanation of the dependency bump
Impact of Change	❌	Describe user, developer, and system impact
Test Plan	⚠️	Add a manual test explanation or automated test reference
Contributors	✅
Screenshots/Videos	✅

---

Overall: the PR title is good, but the body needs the required fields filled in before approval. I also advise a medium risk rating for this dependency/security update.

---

Last updated: Fri, 19 Jun 2026 07:40:51 GMT

[github-actions]

📊 Coverage check completed. See workflow run for details.