Bump jsdom from 27.4.0 to 28.0.0

[dependabot]

Bumps jsdom from 27.4.0 to 28.0.0.

Release notes

Sourced from jsdom's releases.

Version 28.0.0

• Overhauled resource loading customization. See the new README for details on the new API.
• Added MIME type sniffing to <iframe> and <frame> loads.
• Regression: WebSockets are no longer correctly throttled to one connection per origin. This is a result of the bug at nodejs/undici#4743.
• Fixed decoding of the query components of <a> and <area> elements in non-UTF-8 documents.
• Fixed XMLHttpRequest fetches and WebSocket upgrade requests to be interceptable by the new customizable resource loading. (Except synchronous XMLHttpRequests.)
• Fixed the referrer of a document to be set correctly when redirects are involved; it is now the initiating page, not the last hop in the redirect chain.
• Fixed correctness bugs when passing ArrayBuffers or typed arrays to various APIs, where they would not correctly snapshot the data.
• Fixed require("url").parse() deprecation warning when using WebSockets.
• Fixed <iframe>, <frame>, and <img> (when canvas is installed) to fire load events, not error events, on non-OK HTTP responses.
• Fixed many small issues in XMLHttpRequest.

Changelog

Sourced from jsdom's changelog.

28.0.0

• Overhauled resource loading customization. See the new README for details on the new API.
• Added MIME type sniffing to <iframe> and <frame> loads.
• Regression: WebSockets are no longer correctly throttled to one connection per origin. This is a result of the bug at nodejs/undici#4743.
• Fixed decoding of the query components of <a> and <area> elements in non-UTF-8 documents.
• Fixed XMLHttpRequest fetches and WebSocket upgrade requests to be interceptable by the new customizable resource loading. (Except synchronous XMLHttpRequests.)
• Fixed the referrer of a document to be set correctly when redirects are involved; it is now the initiating page, not the last hop in the redirect chain.
• Fixed correctness bugs when passing ArrayBuffers or typed arrays to various APIs, where they would not correctly snapshot the data.
• Fixed require("url").parse() deprecation warning when using WebSockets.
• Fixed <iframe>, <frame>, and <img> (when canvas is installed) to fire load events, not error events, on non-OK HTTP responses.
• Fixed many small issues in XMLHttpRequest.

Commits

• 20f614d Version 28.0.0
• 2b65c6a Replace the resource loader API
• 638bd68 Decode <a> and <area> query strings using document's encoding
• 457bd4b Add AGENTS.md (and CLAUDE.md)
• bf1dc15 Mark header-values tests as fail-slow due to Node.js bug
• 92f269e Update dependencies and dev dependencies
• 7d6e667 Improve spec alignment of Headers and header type tests
• 2c29aed Fix Windows-specific task kill timeouts
• d941216 Add failing regression test for animation-name case-sensitivity
• 56a833d Update style benchmark
• Additional commits viewable 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[dependabot]

Labels

The following labels could not be found: dependencies, npm. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	jsdom@​27.4.0 ⏵ 28.0.0	+4		+1	+5

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Network access: npm undici in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/undici@7.20.0 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Embedded URLs or IPs: npm @acemir/cssom URLs: http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSStyleDeclaration, http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSStyleDeclaration-getPropertyValue, http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSStyleDeclaration-setProperty, http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSStyleDeclaration-removeProperty, http://dev.w3.org/csswg/cssom/#the-cssrule-interface, http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSRule, https://drafts.csswg.org/cssom/#the-cssrulelist-interface, https://drafts.csswg.org/css-nesting-1/, https://drafts.csswg.org/cssom/#the-cssgroupingrule-interface, https://www.w3.org/TR/cssom-1/#dom-cssgroupingrule-insertrule, https://www.w3.org/TR/cssom-1/#dom-cssgroupingrule-deleterule, https://drafts.csswg.org/css-counter-styles/#the-csscounterstylerule-interface, https://drafts.css-houdini.org/css-properties-values-api/#the-css-property-rule-interface, https://www.w3.org/TR/css-conditional-3/#the-cssconditionrule-interface, http://dev.w3.org/csswg/cssom/#cssstylerule, http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSStyleRule, http://dev.w3.org/csswg/cssom/#the-medialist-interface, http://dev.w3.org/csswg/cssom/#cssmediarule, http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSMediaRule, https://opensource.apple.com/source/WebCore/WebCore-7611.1.21.161.3/css/CSSMediaRule.cpp, https://drafts.csswg.org/css-contain-3/, https://www.w3.org/TR/css-contain-3/, https://drafts.csswg.org/css-conditional-3/#the-csssupportsrule-interface, http://dev.w3.org/csswg/cssom/#cssimportrule, http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSImportRule, https://drafts.csswg.org/cssom/#the-cssnamespacerule-interface, http://dev.w3.org/csswg/cssom/#css-font-face-rule, http://www.opensource.apple.com/source/WebCore/WebCore-955.66.1/css/WebKitCSSFontFaceRule.cpp, http://www.w3.org/TR/shadow-dom/#host-at-rule, http://html5index.org/Shadow%20DOM%20-%20CSSHostRule.html, http://dev.w3.org/csswg/cssom/#the-stylesheet-interface, http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSStyleSheet, http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSStyleSheet-insertRule, http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSStyleSheet-deleteRule, https://www.w3.org/TR/cssom-1/#dom-cssstylesheet-replace, https://www.w3.org/TR/cssom-1/#dom-cssstylesheet-replacesync, http://www.w3.org/TR/css3-animations/#DOM-CSSKeyframesRule, http://www.opensource.apple.com/source/WebCore/WebCore-955.66.1/css/WebKitCSSKeyframesRule.cpp, https://www.w3.org/TR/css-animations-1/#dom-csskeyframesrule-appendrule, https://www.w3.org/TR/css-animations-1/#dom-csskeyframesrule-deleterule, https://www.w3.org/TR/css-animations-1/#dom-csskeyframesrule-findrule, http://www.w3.org/TR/css3-animations/#DOM-CSSKeyframeRule, http://www.opensource.apple.com/source/WebCore/WebCore-955.66.1/css/WebKitCSSKeyframeRule.cpp, https://developer.mozilla.org/en/CSS/@-moz-document, http://www.w3.org/TR/DOM-Level-2-Style/css.html#CSS-CSSValue, http://msdn.microsoft.com/en-us/library/ms537634, https://drafts.csswg.org/css-cascade-6/#cssscoperule, https://drafts.csswg.org/css-cascade-5/#csslayerblockrule, https://drafts.csswg.org/css-cascade-5/#csslayerstatementrule, https://drafts.csswg.org/cssom/#the-csspagerule-interface Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/@acemir/cssom@0.9.31 ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@acemir/cssom@0.9.31. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Embedded URLs or IPs: npm @exodus/bytes URLs: https://encoding.spec.whatwg.org/#shift_jis-decoder, https://encoding.spec.whatwg.org/#gbk-decoder, https://encoding.spec.whatwg.org/#gb18030-decoder, https://github.com/ExodusOSS/bytes/blob/main/README.md, https://bugzilla.mozilla.org/show_bug.cgi?id=1994067, https://encoding.spec.whatwg.org/#encode-and-flush, https://encoding.spec.whatwg.org/#decode, https://encoding.spec.whatwg.org/#replacement-decoder, https://encoding.spec.whatwg.org/#names-and-labels, https://unicode.org/Public/MAPPINGS/ISO8859/8859-9.txt, https://npmjs.com/text-encoding, https://webidl.spec.whatwg.org/#idl-DOMString, https://webidl.spec.whatwg.org/#idl-USVString Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/@exodus/bytes@1.11.0 ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@exodus/bytes@1.11.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Embedded URLs or IPs: npm undici URLs: https://www.rfc-editor.org/rfc/rfc9111.html#name-validation, https://www.rfc-editor.org/rfc/rfc9111.html#name-handling-a-validation-respo, https://datatracker.ietf.org/doc/html/rfc5861#section-4, https://datatracker.ietf.org/doc/html/rfc8441#section-4, https://tools.ietf.org/html/rfc7540#section-8.3, https://tools.ietf.org/html/rfc7231#section-4.3.1, https://tools.ietf.org/html/rfc7231#section-4.3.2, https://tools.ietf.org/html/rfc7231#section-4.3.5, https://tools.ietf.org/html/rfc7230#section-3.3.2, https://www.rfc-editor.org/rfc/rfc7230#section-3.3.2, https://github.com/nodejs/undici/issues/2046, https://github.com/nodejs/undici/issues/258, https://www.rfc-editor.org/rfc/rfc9111.html#name-storing-responses-to-authen, https://www.rfc-editor.org/rfc/rfc9111.html#section-3, https://www.rfc-editor.org/rfc/rfc9111.html#section-4.1-5, https://www.rfc-editor.org/rfc/rfc9111.html#section-5.2.2.10-3, https://www.rfc-editor.org/rfc/rfc9111.html#section-5.3, https://www.rfc-editor.org/rfc/rfc9111.html#name-calculating-heuristic-fresh, https://www.rfc-editor.org/rfc/rfc8246.html#section-2.2, https://www.rfc-editor.org/rfc/rfc9111.html#name-max-stale, https://www.rfc-editor.org/rfc/rfc9111.html#section-5.2.1.3, https://www.rfc-editor.org/rfc/rfc9111.html#section-5.2.1.1, https://developer.mozilla.org/en-US/docs/Web/HTTP/Status, https://tools.ietf.org/html/rfc7231#section-6.4.2, https://fetch.spec.whatwg.org/#http-redirect-fetch, https://tools.ietf.org/html/rfc7231#section-6.4.4, https://tools.ietf.org/html/rfc7231#section-6.4, https://github.com/node-fetch/fetch-blob/blob/8ab587d34080de94140b54f07168451e7d0b655e/index.js#L229-L241, https://developer.mozilla.org/en-US/docs/Web/API/URL/URL:, https://github.com/nodejs/node/pull/38505/files, https://github.com/nodejs/undici/pull/319, https://tools.ietf.org/html/rfc7230#section-3.2.6, https://github.com/nodejs/node/blob/main/lib/_http_common.js, https://www.rfc-editor.org/rfc/rfc9110#field.content-range, CacheStorage.open, https://mimesniff.spec.whatwg.org/#parse-a-mime-type, https://fetch.spec.whatwg.org/#enumdef-requestduplex, http://fetch.spec.whatwg.org/#forbidden-method, https://github.com/nodejs/undici/issues/2630, https://fetch.spec.whatwg.org/#response-create, https://fetch.spec.whatwg.org/#concept-method-normalize, https://dom.spec.whatwg.org/#dom-abortsignal-any, https://github.com/nodejs/undici/issues/1926., https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry, https://httpwg.org/specs/rfc9110.html#preferred.date.format, https://httpwg.org/specs/rfc9110.html#obsolete.date.formats, https://datatracker.ietf.org/doc/html/rfc6265#section-5.1.1, https://www.rfc-editor.org/rfc/rfc9111.html#section-5.2.3-1, https://www.rfc-editor.org/rfc/rfc9110.html#name-etag, https://tools.ietf.org/html/rfc2616, https://tools.ietf.org/html/rfc7230, https://github.com/chromium/chromium/blob/94.0.4604.1/third_party/blink/renderer/core/fetch/response.cc#L116, https://fetch.spec.whatwg.org/#header-name, https://fetch.spec.whatwg.org/#header-value, https://w3c.github.io/webappsec-referrer-policy/#parse-referrer-policy-from-header, https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy#specify_a_fallback_policy, https://w3c.github.io/webappsec-referrer-policy/#set-requests-referrer-policy-on-redirect, https://fetch.spec.whatwg.org/#cross-origin-resource-policy-check, https://fetch.spec.whatwg.org/#concept-cors-check, https://fetch.spec.whatwg.org/#concept-tao-check, https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-dest-header, https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-mode-header, https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-site-header, https://w3c.github.io/webappsec-fetch-metadata/#sec-fetch-user-header, https://fetch.spec.whatwg.org/#append-a-request-origin-header, https://html.spec.whatwg.org/multipage/origin.html#clone-a-policy-container, https://w3c.github.io/webappsec-referrer-policy/#determine-requests-referrer, https://webidl.spec.whatwg.org/#iterator-result, https://webidl.spec.whatwg.org/#dfn-iterator-prototype-object, https://fetch.spec.whatwg.org/#body-fully-read, https://streams.spec.whatwg.org/#readablestreamdefaultreader-read-all-bytes, https://streams.spec.whatwg.org/#read-loop, https://fetch.spec.whatwg.org/#is-local, https://fetch.spec.whatwg.org/#simple-range-header-value, https://fetch.spec.whatwg.org/#build-a-content-range, https://html.spec.whatwg.org/multipage/webappapis.html#environment-settings-object, https://html.spec.whatwg.org/multipage/server-sent-events.html#sse-processing-model, https://github.com/web-platform-tests/wpt/commit/e4c5cc7a5e48093220528dfdd1c4012dc3837a0e, https://mimesniff.spec.whatwg.org/#http-quoted-string-token-code-point, https://fetch.spec.whatwg.org/#data-url-processor, https://fetch.spec.whatwg.org/#data-url-struct, https://url.spec.whatwg.org/#concept-url-serializer, https://url.spec.whatwg.org/#string-percent-decode, https://url.spec.whatwg.org/#percent-decode, https://mimesniff.spec.whatwg.org/#http-token-code-point, https://mimesniff.spec.whatwg.org/#mime-type, https://mimesniff.spec.whatwg.org/#mime-type-essence, https://fetch.spec.whatwg.org/#http-whitespace, https://fetch.spec.whatwg.org/#collect-an-http-quoted-string, https://fetch.spec.whatwg.org/#example-http-quoted-string, https://mimesniff.spec.whatwg.org/#serialize-a-mime-type, https://mimesniff.spec.whatwg.org/#minimize-a-supported-mime-type, https://datatracker.ietf.org/doc/html/rfc6455#section-6.1, https://datatracker.ietf.org/doc/html/rfc6455#section-5.2, https://websockets.spec.whatwg.org/#feedback-from-the-protocol, https://datatracker.ietf.org/doc/html/rfc6455#section-9.1, https://datatracker.ietf.org/doc/html/rfc6455#section-1.9, https://www.rfc-editor.org/rfc/rfc7231#section-7.1.1.1, https://www.rfc-editor.org/rfc/rfc6265#section-4.1.1, https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-prefixes-00#section-3.1, https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-prefixes-00#section-3.2, https://www.rfc-editor.org/rfc/rfc9111.html#section-3-5, https://tools.ietf.org/html/rfc7230#section-6.3.2, https://github.com/curl/curl/blob/3434c6b46e682452973972e8313613dfa58cd690/lib/mime.c#L1029-L1030, https://github.com/form-data/form-data/issues/63, https://fetch.spec.whatwg.org/#bodyinit-safely-extract, https://fetch.spec.whatwg.org/#concept-body-clone, https://fetch.spec.whatwg.org/#concept-body-consume-body, https://fetch.spec.whatwg.org/#body-unusable, https://fetch.spec.whatwg.org/#concept-body-mime-type, https://fetch.spec.whatwg.org/#concept-main-fetch, https://fetch.spec.whatwg.org/#concept-scheme-fetch, https://github.com/nodejs/undici/issues/1776, https://github.com/web-platform-tests/wpt/blob/7b0ebaccc62b566a1965396e5be7bb2bc06f841f/FileAPI/url/resources/fetch-tests.js#L52-L56, https://github.com/nodejs/undici/issues/1193., https://fetch.spec.whatwg.org/#cors-non-wildcard-request-header-name, https://fetch.spec.whatwg.org/#authentication-entries, https://github.com/whatwg/fetch/issues/1293, https://fetch.spec.whatwg.org/#http-network-fetch, https://dom.spec.whatwg.org/#concept-event-fire, https://andreubotella.github.io/multipart-form-data/#multipart-form-data-parser, https://andreubotella.github.io/multipart-form-data/#parse-multipart-form-data-headers, https://whatpr.org/websockets/48.html#close-the-websocket, https://developer.mozilla.org/en-US/docs/Web/API/Blob, https://developer.mozilla.org/en-US/docs/Web/API/File Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/undici@7.20.0 ℹ Read more on: This package | This alert | What are URL strings? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: npm undici reads JEST_WORKER_ID Env Vars: JEST_WORKER_ID Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/undici@7.20.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: npm undici reads UNDICI_NO_WASM_SIMD Env Vars: UNDICI_NO_WASM_SIMD Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/undici@7.20.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: npm undici reads http_proxy Env Vars: http_proxy Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/undici@7.20.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: npm undici reads HTTP_PROXY Env Vars: HTTP_PROXY Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/undici@7.20.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: npm undici reads https_proxy Env Vars: https_proxy Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/undici@7.20.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: npm undici reads HTTPS_PROXY Env Vars: HTTPS_PROXY Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/undici@7.20.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: npm undici reads no_proxy Env Vars: no_proxy Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/undici@7.20.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: npm undici reads NO_PROXY Env Vars: NO_PROXY Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/undici@7.20.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Minified code present: npm undici with 96.0% likelihood Confidence: 0.96 Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/undici@7.20.0 ℹ Read more on: This package | This alert | What's wrong with minified code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: In many cases minified code is harmless, however minified code can be used to hide a supply chain attack. Consider not shipping minified code on npm. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		Environment variable access: npm undici reads CI Env Vars: CI Location: Package overview From: package-lock.json → npm/jsdom@28.0.0 → npm/undici@7.20.0 ℹ Read more on: This package | This alert | What is environment variable access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/undici@7.20.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[guibranco]

Automatically approved by gstraccini[bot]

[deepsource-io]

Here's the code health analysis summary for commits 0627f41..9976173. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗
Secrets	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

2026-02-02T19:10:23Z INF scanning for exposed secrets...
7:10PM INF 498 commits scanned.
2026-02-02T19:10:23Z INF scan completed in 596ms
2026-02-02T19:10:23Z INF no leaks found