[Snyk] Fix for 2 vulnerabilities

[naiba4]

Snyk has created this PR to fix 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• website/package.json
• website/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Prototype Pollution SNYK-JS-AXIOS-15252993	170
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	157

---

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9e7ef2c

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

[guardrails]

⚠️ We detected 1 security issue in this pull request:

Vulnerable Libraries (1)

Severity	Details
Medium	pkg:npm/lodash-es@4.17.21 (t) upgrade to: 4.17.23

More info on how to fix Vulnerable Libraries in JavaScript.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[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

[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 defer-to-connect in module tls Module: tls Location: Package overview From: ? → npm/defer-to-connect@1.1.3 ℹ 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/defer-to-connect@1.1.3. 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		Network access: npm raw-body in module http-errors Module: http-errors Location: Package overview From: ? → npm/raw-body@2.5.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/raw-body@2.5.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		Environment variable access: npm @babel/code-frame reads FORCE_COLOR Env Vars: FORCE_COLOR Location: Package overview From: ? → npm/@babel/code-frame@7.29.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/@babel/code-frame@7.29.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 @babel/core URLs: https://babeljs.io/docs/en/options#filename, http://babeljs.io/docs/plugins/external-helpers/, http://babeljs.io/docs/plugins/transform-react-jsx/, http://babeljs.io/docs/plugins/#modules, http://babeljs.io/docs/plugins/preset-react/, http://babeljs.io/docs/plugins/#presets, https://babeljs.io/docs/en/babel-core/#options, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-async-do-expressions, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-decimal, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-decorators, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-decorators, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-do-expressions, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-do-expressions, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-export-default-from, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-export-default-from, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-flow, https://github.com/babel/babel/tree/main/packages/babel-preset-flow, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-function-bind, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-function-bind, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-function-sent, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-function-sent, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-jsx, https://github.com/babel/babel/tree/main/packages/babel-preset-react, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-pipeline-operator, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-pipeline-operator, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-record-and-tuple, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-throw-expressions, https://github.com/babel/babel/tree/main/packages/babel-plugin-proposal-throw-expressions, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-typescript, https://github.com/babel/babel/tree/main/packages/babel-preset-typescript, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-async-generators, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-async-generator-functions, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-class-properties, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-class-properties, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-private-methods, https://github.com/babel/babel/tree/HEAD/packages/babel-plugin-syntax-class-static-block, https://github.com/babel/babel/tree/HEAD/packages/babel-plugin-transform-class-static-block, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-dynamic-import, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-export-namespace-from, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-export-namespace-from, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-import-assertions, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-import-attributes, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-import-meta, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-logical-assignment-operators, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-logical-assignment-operators, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-module-string-names, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-numeric-separator, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-numeric-separator, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-nullish-coalescing-operator, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-nullish-coalescing-opearator, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-object-rest-spread, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-object-rest-spread, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-optional-catch-binding, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-optional-catch-binding, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-optional-chaining, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-optional-chaining, https://github.com/babel/babel/tree/main/packages/babel-plugin-syntax-private-property-in-object, https://github.com/babel/babel/tree/main/packages/babel-plugin-transform-private-property-in-object, https://github.com/babel/babel/blob/main/packages/babel-plugin-syntax-unicode-sets-regex/README.md, https://github.com/babel/babel/blob/main/packages/babel-plugin-proposalunicode-sets-regex/README.md Location: Package overview From: ? → npm/@babel/core@7.29.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/@babel/core@7.29.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 @babel/core is 100.0% likely to have a medium risk anomaly Notes: The examined code is a standard, benign helper for constructing and wrapping configuration items from descriptors within Babel’s tooling. There is no evidence of data leakage, exfiltration, backdoors, or other malicious activity in this fragment. The combination of immutability, brand-based identity, and non-enumerable descriptor storage indicates a well-scoped internal utility rather than anything suspicious. Confidence: 1.00 Severity: 0.60 From: ? → npm/@babel/core@7.29.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/@babel/core@7.29.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 @babel/helper-module-transforms is 100.0% likely to have a medium risk anomaly Notes: The code is a legitimate, static-code transformation utility used in Babel to ensure proper behavior of ES module bindings after transforms. There is no evidence of malicious behavior, data leakage, or external communications within this fragment. It operates purely on AST-level transformations consistent with module import/export handling. Confidence: 1.00 Severity: 0.60 From: ? → npm/@babel/helper-module-transforms@7.28.6 ℹ 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/@babel/helper-module-transforms@7.28.6. 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 @babel/helpers URLs: body.0.id, body.1.id, body.0.declarations.0.id, body.2.id, body.3.id, body.4.id, body.5.id, body.6.id, body.7.id, https://github.com/babel/babel/blob/main/packages/babel-helpers/LICENSE, body.8.id, body.9.id, body.10.id, body.11.id, body.12.id, body.13.id, body.1.declarations.0.id Location: Package overview From: ? → npm/@babel/helpers@7.28.6 ℹ 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/@babel/helpers@7.28.6. 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 @babel/helpers is 100.0% likely to have a medium risk anomaly Notes: The analyzed fragment is a conventional Babel/TypeScript-style decorators runtime (applyDecs) responsible for applying decorators to class members and managing metadata and initializers. There is no evidence of malware, backdoors, or external data leakage within this module. While complex, the code behaves as a metadata-driven decorator processor and should be considered low risk when used as intended. Downstream risks depend on the decorators provided by consumers, not this utility itself. Confidence: 1.00 Severity: 0.60 From: ? → npm/@babel/helpers@7.28.6 ℹ 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/@babel/helpers@7.28.6. 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 @babel/types with super.foo URLs: super.foo Location: Package overview From: ? → npm/@babel/types@7.29.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/@babel/types@7.29.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		Debug access: npm @docusaurus/logger in module async_hooks Module: async_hooks Location: Package overview From: ? → npm/@docusaurus/logger@3.9.2 ℹ 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/@docusaurus/logger@3.9.2. 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 @docusaurus/logger reads DOCUSAURUS_PERF_LOGGER Env Vars: DOCUSAURUS_PERF_LOGGER Location: Package overview From: ? → npm/@docusaurus/logger@3.9.2 ℹ 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/@docusaurus/logger@3.9.2. 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 @docusaurus/mdx-loader URLs: https://github.com/facebook/docusaurus/pull/9394, https://github.com/facebook/docusaurus/pull/9684#discussion_r1457595181, https://github.com/facebook/docusaurus/issues/11003#issuecomment-2733925363, https://github.com/facebook/docusaurus/pull/8288#discussion_r1125871405, https://github.com/yarnpkg/berry/pull/3889#issuecomment-1034469784, https://github.com/facebook/docusaurus/issues/6370, https://github.com/facebook/docusaurus/issues/10544#issuecomment-2390943794, https://github.com/facebook/docusaurus/pull/10553, https://github.com/domdomegg/recma-mdx-displayname, https://github.com/facebook/docusaurus/pull/8960, https://github.com/mdx-js/mdx/pull/2295#issuecomment-1540085960, https://github.com/project/README.md Location: Package overview From: ? → npm/@docusaurus/mdx-loader@3.9.2 ℹ 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/@docusaurus/mdx-loader@3.9.2. 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 @docusaurus/types URLs: CurrentBundler.name, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/calendar, docusaurus.io, https://github.com/facebook/docusaurus/pull/9954, doc1.md, https://facebook.github.io, https://docusaurus.io, https://docusaurus.io/docs/api/docusaurus-config#favicon, https://github.com/slorber/trailing-slash-guide, https://docusaurus.io/docs/api/docusaurus-config#trailingSlash, https://docusaurus.io/docs/i18n/introduction, https://docusaurus.io/docs/api/docusaurus-config#i18n, https://remix.run/blog/future-flags, https://moz.com/learn/seo/robots-meta-directives, https://docusaurus.io/docs/api/docusaurus-config#noIndex, https://docusaurus.io/docs/api/docusaurus-config#onBrokenLinks, https://docusaurus.io/docs/api/docusaurus-config#onBrokenAnchors, https://docusaurus.io/docs/api/docusaurus-config#onBrokenMarkdownLinks, https://docusaurus.io/docs/creating-pages#duplicate-routes, https://docusaurus.io/docs/api/docusaurus-config#onDuplicateRoutes, https://docusaurus.io/docs/api/docusaurus-config#tagline, myDoc.md, https://docusaurus.io/docs/api/docusaurus-config#projectName, https://docusaurus.io/docs/api/docusaurus-config#githubHost, https://docusaurus.io/docs/api/docusaurus-config#staticDirectories, https://docusaurus.io/docs/api/docusaurus-config#head, https://docusaurus.io/docs/api/docusaurus-config#scripts, https://docusaurus.io/docs/api/docusaurus-config#stylesheets, https://docusaurus.io/docs/advanced/client#client-modules, https://docusaurus.io/docs/api/docusaurus-config#clientModules, https://docusaurus.io/docs/api/docusaurus-config#baseUrlIssueBanner, https://docusaurus.io/docs/typescript-support Location: Package overview From: ? → npm/@docusaurus/types@3.9.2 ℹ 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/@docusaurus/types@3.9.2. 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		Filesystem access: npm @docusaurus/utils-validation with module fs-extra Module: fs-extra Location: Package overview From: ? → npm/@docusaurus/utils-validation@3.9.2 ℹ Read more on: This package | This alert | What is filesystem 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: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@docusaurus/utils-validation@3.9.2. 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 @docusaurus/utils URLs: xyz.md, https://github.com/facebook/docusaurus/pull/4222#issuecomment-795517329, https://domain.com, https://example.com, github.com:facebook/docusaurus.git, index.md, brokenFile.md, https://github.com/sindresorhus/slash/blob/main/index.js, https://github.com/facebook/docusaurus/pull/10022, https://github.com/mdx-js/mdx/issues/701#issuecomment-947030041, https://github.com/remarkjs/remark-directive, https://talk.commonmark.org/t/generic-directives-plugins-syntax/444, https://github.com/jonschlinkert/gray-matter/blob/ce67a86dba419381db0dd01cc84e2d30a1d1e6a5/index.js#L39 Location: Package overview From: ? → npm/@docusaurus/utils@3.9.2 ℹ 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/@docusaurus/utils@3.9.2. 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 @docusaurus/utils is 100.0% likely to have a medium risk anomaly Notes: The module is a benign, well-scoped utility for deterministic, URL-friendly naming with collision-avoidance. MD5 usage is acceptable here given the non-security-critical purpose, though migration to a stronger hash could be considered if future requirements demand cryptographic strength. Overall risk remains low with respect to data leakage or code behavior; the primary concern is MD5's weaknesses and potential policy guidance on hashing algorithms. Confidence: 1.00 Severity: 0.60 From: ? → npm/@docusaurus/utils@3.9.2 ℹ 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/@docusaurus/utils@3.9.2. 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 @docusaurus/utils Location: Package overview From: ? → npm/@docusaurus/utils@3.9.2 ℹ 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/@docusaurus/utils@3.9.2. 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 colord with 100.0% likelihood Confidence: 1.00 Location: Package overview From: ? → npm/colord@2.9.2 ℹ 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/colord@2.9.2. 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 colord is 100.0% likely to have a medium risk anomaly Notes: The code constitutes a focused HWB color space utility that converts RGBA to HWB and parses HWB strings, exposing conversion helpers via prototype augmentation. There is no direct evidence of malicious activity (no network/file I/O, no data leakage to unknown sinks). The main security considerations are prototype pollution risks due to prototype augmentation and the potential for side effects in environments that rely on Object.prototype stability; otherwise, the fragment appears benign as a color conversion utility. Confidence: 1.00 Severity: 0.60 From: ? → npm/colord@2.9.2 ℹ 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/colord@2.9.2. 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		Publisher changed: npm convert-source-map is now published by phated instead of thlorenz New Author: phated Previous Author: thlorenz From: ? → npm/convert-source-map@2.0.0 ℹ Read more on: This package | This alert | What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/convert-source-map@2.0.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 convert-source-map URLs: https://github.com/thlorenz/convert-source-map#upgrading Location: Package overview From: ? → npm/convert-source-map@2.0.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/convert-source-map@2.0.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 escalade is 100.0% likely to have a medium risk anomaly Notes: This is a generic upward-directory traversal utility. It is not inherently malicious. Security posture hinges on the callback's implementation and proper termination guarantees. Risks include unhandled filesystem errors and potential unbounded traversal if the callback misbehaves or lacks proper termination checks. Confidence: 1.00 Severity: 0.60 From: ? → npm/escalade@3.1.1 ℹ 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/escalade@3.1.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		Filesystem access: npm escalade with module fs Module: fs Location: Package overview From: ? → npm/escalade@3.1.1 ℹ Read more on: This package | This alert | What is filesystem 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: If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/escalade@3.1.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.
See 20 more rows in the dashboard

View full report