Skip to content

[Snyk] Security upgrade @docusaurus/preset-classic from 0.0.0-5591 to 3.8.1#5664

Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-ad47a14607f57053c5694552ff82f703
Closed

[Snyk] Security upgrade @docusaurus/preset-classic from 0.0.0-5591 to 3.8.1#5664
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-ad47a14607f57053c5694552ff82f703

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Jun 6, 2025

snyk-top-banner

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

Snyk changed the following file(s):

  • microsite/package.json

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.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Improper Input Validation
SNYK-JS-POSTCSS-5926692
  479  

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:

🦉 Improper Input Validation

Summary by Sourcery

Bug Fixes:

  • Bump @docusaurus/preset-classic from 0.0.0-5591 to 3.8.1 to fix the SNYK-JS-POSTCSS-5926692 improper input validation vulnerability.

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Jun 6, 2025

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented Jun 6, 2025

Reviewer's Guide

Automated bump of @docusaurus/preset-classic to v3.8.1 in package.json to resolve a medium-severity improper input validation vulnerability reported by Snyk.

Class Diagram: Updated dependencies in microsite/package.json

classDiagram
  class microsite_dependencies {
    <<JSON Object: package.json dependencies>>
    "@docusaurus/core": "0.0.0-5591"
    "@docusaurus/plugin-client-redirects": "0.0.0-5591"
    "@docusaurus/preset-classic": "3.8.1"
    "@swc/core": "^1.3.46"
    "clsx": "^1.1.1"
    "docusaurus-plugin-sass": "^0.2.3"
    %% Other dependencies in microsite/package.json are not shown as they were not part of this specific PR's focus on @docusaurus/preset-classic update.
  }
Loading

Flow Diagram: Snyk Automated Security Upgrade Process

graph TD
    A["Snyk Service"] -- "Scans 'microsite' project\nfor vulnerabilities" --> B["Identifies Vulnerability\n(SNYK-JS-POSTCSS-5926692)\nin '@docusaurus/preset-classic v0.0.0-5591'"];
    B -- "Automatically" --> C["Creates Pull Request\n(This PR)"];
    C -- "Proposes update in 'microsite/package.json'" --> D["Dependency Change:\n'@docusaurus/preset-classic'\nFrom: '0.0.0-5591'\nTo: '3.8.1'"];
    D -- "After Developer Review & Merge" --> E["Dependency '@docusaurus/preset-classic' is upgraded"];
    E --> F["Security vulnerability resolved"];
Loading

File-Level Changes

Change Details Files
Upgrade @docusaurus/preset-classic to fix improper input validation vulnerability
  • Changed version specifier from 0.0.0-5591 to 3.8.1 in dependencies
  • Locked file (yarn.lock) update failed automatically and must be refreshed manually
microsite/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@socket-security
Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert (click for details)
Warn High
caniuse-lite@1.0.30001481 has a License Policy Violation.

License: CC-BY-4.0 (npm metadata)

License: CC-BY-4.0 (package/LICENSE)

License: CC-BY-4.0 (package/package.json)

From: microsite/yarn.locknpm/browserslist@4.21.5npm/caniuse-lite@1.0.30001481

ℹ Read more on: This package | This alert | What is a license policy violation?

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: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

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

Comment thread microsite/package.json
Comment on lines 32 to +34
"@docusaurus/core": "0.0.0-5591",
"@docusaurus/plugin-client-redirects": "0.0.0-5591",
"@docusaurus/preset-classic": "0.0.0-5591",
"@docusaurus/preset-classic": "3.8.1",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR updates @docusaurus/preset-classic to version 3.8.1 while leaving related Docusaurus packages at version 0.0.0-5591. Docusaurus packages are designed to work together at matching versions, and mixing versions (especially across major versions) will likely cause compatibility issues.

Recommendation: Update all Docusaurus packages to the same version (3.8.1):

"@docusaurus/core": "3.8.1",
"@docusaurus/plugin-client-redirects": "3.8.1",
"@docusaurus/preset-classic": "3.8.1",

This ensures proper compatibility and will fully address the security vulnerability while maintaining a stable build.

Suggested change
"@docusaurus/core": "0.0.0-5591",
"@docusaurus/plugin-client-redirects": "0.0.0-5591",
"@docusaurus/preset-classic": "0.0.0-5591",
"@docusaurus/preset-classic": "3.8.1",
"@docusaurus/core": "3.8.1",
"@docusaurus/plugin-client-redirects": "3.8.1",
"@docusaurus/preset-classic": "3.8.1",

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Jun 6, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

@github-actions
Copy link
Copy Markdown

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Jun 13, 2025
@github-actions github-actions Bot closed this Jun 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants