Skip to content

chore(deps): bump @docusaurus/plugin-content-docs from 3.10.1 to 3.10.2#2988

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/docusaurus/plugin-content-docs-3.10.2
Open

chore(deps): bump @docusaurus/plugin-content-docs from 3.10.1 to 3.10.2#2988
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/docusaurus/plugin-content-docs-3.10.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 19, 2026

Copy link
Copy Markdown
Contributor

Bumps @docusaurus/plugin-content-docs from 3.10.1 to 3.10.2.

Release notes

Sourced from @​docusaurus/plugin-content-docs's releases.

3.10.2 (2026-07-10)

Backport and cherry-pick commits from main for v3.10.2 patch release:

Changelog

Sourced from @​docusaurus/plugin-content-docs's changelog.

3.10.2 (2026-07-10)

Backport and cherry-pick commits from main for v3.10.2 patch release:

Commits

Dependabot compatibility score

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)

Bumps [@docusaurus/plugin-content-docs](https://github.com/facebook/docusaurus/tree/HEAD/packages/docusaurus-plugin-content-docs) from 3.10.1 to 3.10.2.
- [Release notes](https://github.com/facebook/docusaurus/releases)
- [Changelog](https://github.com/facebook/docusaurus/blob/main/CHANGELOG.md)
- [Commits](https://github.com/facebook/docusaurus/commits/v3.10.2/packages/docusaurus-plugin-content-docs)

---
updated-dependencies:
- dependency-name: "@docusaurus/plugin-content-docs"
  dependency-version: 3.10.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Jul 19, 2026

Copy link
Copy Markdown
Contributor Author

Assignees

The following users could not be added as assignees: protocol-galileo. Either the username does not exist or it does not have the correct permissions to be added as an assignee.

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

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 19, 2026
@dependabot
dependabot Bot requested review from a team as code owners July 19, 2026 04:13
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 19, 2026
@vercel

vercel Bot commented Jul 19, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
metamask-docs Error Error Jul 19, 2026 4:13am

Request Review

@socket-security

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​docusaurus/​plugin-content-docs@​3.10.2991007798100

View full report

@socket-security

Copy link
Copy Markdown

Caution

MetaMask internal reviewing guidelines:

  • Do not ignore-all
  • Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
  • Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
    @SocketSecurity ignore npm/PACKAGE@VERSION
Action Severity Alert  (click "▶" to expand/collapse)
Block Medium
Potential security risk (AI signal): npm @docusaurus/core is 62.0% likely risky

Notes: The snippet implements a webpack-internal HTTP endpoint intended to return internal module source content to the caller using a user-controlled query parameter. While it does not show overt malware behavior (no execution/exfiltration beyond responding to the HTTP client), it creates a high-impact information disclosure risk if exposed without strict access controls and environment gating. The fragment’s incomplete/unset source-map variables reduce certainty about exact returned artifacts, but the source-disclosure flow to res.end is clear.

Confidence: 0.62

Severity: 0.78

From: package-lock.jsonnpm/@docusaurus/plugin-content-docs@3.10.2npm/@docusaurus/core@3.10.2

ℹ Read more on: This package | This alert | What are AI-detected potential security risks?

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 identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@docusaurus/core@3.10.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.

Warn Low
Potential code anomaly (AI signal): npm @docusaurus/utils is 70.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: 0.70

Severity: 0.60

From: package-lock.jsonnpm/@docusaurus/plugin-content-docs@3.10.2npm/@docusaurus/utils@3.10.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.10.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.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants