[Snyk] Security upgrade eslint from 8.57.1 to 9.26.0

[naiba4]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• packages/scripts/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Uncontrolled Recursion SNYK-JS-ESLINT-15102420	60

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
gutenberg	Error		Feb 2, 2026 8:07pm
gutenberg-wd9x	Error		Feb 2, 2026 8:07pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 913b8e4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[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 prettier in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: ? → npm/prettier@3.8.1 ℹ 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/prettier@3.8.1. 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		Debug access: npm @humanwhocodes/module-importer in module module Module: module Location: Package overview From: ? → npm/@humanwhocodes/module-importer@1.0.1 ℹ Read more on: This package | This alert | What is debug 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: Removing the use of debug will reduce the risk of any reflection and dynamic code execution. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@humanwhocodes/module-importer@1.0.1. 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		Dynamic module loading: npm @humanwhocodes/module-importer Location: Package overview From: ? → npm/@humanwhocodes/module-importer@1.0.1 ℹ Read more on: This package | This alert | What is dynamic require? 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 avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@humanwhocodes/module-importer@1.0.1. 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		High entropy strings: npm acorn Location: Package overview From: ? → npm/acorn@8.15.0 ℹ Read more on: This package | This alert | What are high entropy 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: Please inspect these strings to check if they are benign. Maintainers should clarify the purpose and existence of high entropy strings if there is a legitimate purpose. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/acorn@8.15.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		Potential code anomaly (AI signal): npm acorn is 100.0% likely to have a medium risk anomaly Notes: Overall, the analyzed code is a legitimate, well-structured Acorn 8.x parser fragment with robust handling for ES2020+ features. There is no direct malicious payload, backdoor, or exfiltration mechanism within this fragment. The primary security considerations relate to safe handling of untrusted input to avoid DoS via complex/ pathological RegExp usage or verbose error reporting. In a typical extension usage, isolate parsing to a sandbox and limit resource usage to mitigate potential abuse. Confidence: 1.00 Severity: 0.60 From: ? → npm/acorn@8.15.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/acorn@8.15.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		Unmaintained: npm prelude-ls was last published 6 years ago Last Publish: 4/2/2020, 10:53:40 PM From: ? → npm/prelude-ls@1.2.1 ℹ Read more on: This package | This alert | What are unmaintained packages? 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: Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/prelude-ls@1.2.1. 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 prettier URLs: statement_parser.ml, flow_lexer.ml, camlinternalOO.ml, wtf8.ml, flow_sedlexing.ml, parser_env.ml, expression_parser.ml, parser_flow.ml, https://github.com/microsoft/TypeScript/issues/29729#issuecomment-700527227, https://github.com/prettier/prettier/blob/next/src/common/ast-path.js, https://prettier.io/docs/configuration, e.next?.type===, e.openStrip.open?, e.closeStrip.open?, e.inverseStrip.open?, https://yarnpkg.com/en/docs/selective-version-resolutions, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode., https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/, https://aka.ms/tsconfig, https://typescript-eslint.io/troubleshooting/faqs/general#the-key-property-is-deprecated-on-type-nodes-use-key-instead-warnings., https://git.io/vg5Ft, contents.lr, text.md, css.global, n.rest?, n.id?, https://www.w3.org/TR/html5/syntax.html#closing-elements-that-have-implied-end-tags, https://registry.npmjs.org/, SemVer.compare, https://github.com/jedmao/, http://treyhunner.com, git://github.com/editorconfig/editorconfig-core-js.git, https://github.com/editorconfig/editorconfig-core-js/issues, https://git-scm.com/docs/gitignore, https://git-scm.com/docs/gitignore/2.22.1, e.property?e.property.type===, https://evilmartians.com/chronicles/postcss-8-plugin-migration, t.value.group?.type===, t.open?.value===, https://prettier.io/docs/plugins#optional-embed Location: Package overview From: ? → npm/prettier@3.8.1 ℹ 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/prettier@3.8.1. 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 ws URLs: https://html.spec.whatwg.org/multipage/comms.html#the-websocket-interface, https://github.com/websockets/ws/issues/1869., https://github.com/websockets/ws/issues/1940. Location: Package overview From: ? → npm/ws@8.19.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/ws@8.19.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 zod URLs: z.date, 127.0.0.1, gmail.com, https://stackoverflow.com/a/46181/1550155, https://thekevinscott.com/emojis-in-javascript/#writing-a-regular-expression, https://stackoverflow.com/questions/7860392/determine-if-string-is-in-base64-using-javascript, https://base64.guru/standards/base64url, https://stackoverflow.com/a/3143231, https://stackoverflow.com/questions/3966484/why-does-modulus-operator-return-fractional-number-in-javascript/31711034#31711034, lkajsdf.com, domain.com, firstname.lastname@domain.com, subdomain.domain.com, domain-one.com, domain.name, domain.co.jp, very.common@example.com, disposable.style.email.with+symbol@example.com, other.email-with-hyphen@example.com, example.com, user.name+tag+sorting@example.com, asdf.example.com, strange-example.com, example.org, my-example.com, b.cd, mail.com, test.te-st.com, etu.inp-n7.fr, example.com@example.org, test.com, strange.example.com, 123.123.123.123, email.domain.com, -domain.com, Abc.example.com, but_its_not_allowed_in_this_part.example.com, -start.com, http://google.com, https://google.com/asdf?asdf=ljk3lk4&asdf=234#asdf, lkjsdf.com, 122.122.122.122, 254.164.77.1, 114.71.82.94, 0.0.0.0, 37.85.236.115, 192.168.0.1/24, 192.168.0.0/24, 10.0.0.0/8, 203.0.113.0/24, 192.0.2.0/24, 127.0.0.0/8, 172.16.0.0/12, 192.168.1.0/24, 192.168.1.1/33, 10.0.0.1/-1, 192.168.1.1/24/24, 192.168.1.0/abc, user.name, https://my.local, https://example.com, http://example.com, https://example.com:8080, http://example.com:8080, https://sub.example.com, http://sub.example.com, https://example.com/path/to/resource, http://example.com/path/to/resource, https://example.com/path?query=param, http://example.com/path?query=param, https://example.com/path#fragment, http://example.com/path#fragment, ftp://example.com, shttp://example.com, httpz://example.com, http://-asdf.com, http://asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf.com, http://asdf.c, developer.mozilla.org/en-US/docs/Web/API/URL/password, lckj.com, 94.105.123.75, 192.168.0.1, 255.255.255.255, 1.2.3.4, 0.0.0.0/0, 255.255.255.255/32, 192.168.0.0, 192.168.0.0/33, 192.168.0.0/-1, z.coerce.date, z.iso.date, z.map, https://json-schema.org/draft/2020-12/schema, http://json-schema.org/draft-07/schema#, 213.174.246.205, https://speedtest.net, https://example.org, https://example.net.il, https://example.com/, https://example.com/Post.json, https://example.com/User.json, https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/email, https://stackoverflow.com/questions/106179/regular-expression-to-match-dns-hostname-or-ip-address, https://blog.stevenlevithan.com/archives/validate-phone-number#r4-3, e.co, EXAMPLE.COM, z.int, z.lt, z.gt, z.email, https://example.com/path?query=123#fragment, http://example.com/, http://example.com//, http://examples.com, http://example.org, 192.168.1.1 Location: Package overview From: ? → npm/zod@3.25.76 ℹ 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/zod@3.25.76. 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		Potential code anomaly (AI signal): npm zod is 100.0% likely to have a medium risk anomaly Notes: No explicit network exfiltration, reverse shell, or credential theft is present in this fragment. However, the code assembles and compiles arbitrary code via the Function constructor and invokes passed-in functions immediately (twice). That behavior constitutes a strong dangerous primitive (arbitrary code execution) which can be abused if any inputs (strings or args) are attacker-controlled. Treat this module as risky in threat models where inputs are not fully trusted; review call sites and sanitize/validate inputs or avoid dynamic evaluation. Confidence: 1.00 Severity: 0.60 From: ? → npm/zod@3.25.76 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/zod@3.25.76. 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