Skip to content

Conversation

@ioncakephper
Copy link
Owner

@ioncakephper ioncakephper commented Sep 27, 2025

snyk-top-banner

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
high severity Origin Validation Error
SNYK-JS-WEBPACKDEVSERVER-10300775
  142  
medium severity Exposed Dangerous Method or Function
SNYK-JS-WEBPACKDEVSERVER-10300777
  129  

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.

Description by Korbit AI

What change is being made?

Update Docusaurus dependencies to latest patched versions:

  • Upgrade @docusaurus/core from 3.6.3 to 3.9.0
  • Upgrade @docusaurus/preset-classic from 3.6.3 to 3.9.0

Why are these changes being made?

Fix two Snyk-vulnerable dependencies by upgrading to patched releases. This reduces security risk while keeping dependencies aligned.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

Copy link

@korbit-ai korbit-ai bot left a comment

Choose a reason for hiding this comment

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

I've completed my review and didn't find any issues... but I did find this shark.

                (`.
                 \ `.
                  )  `._..---._
\`.       __...---`         o  )
 \ `._,--'           ,    ___,'
  ) ,-._          \  )   _,-'
 /,'    ``--.._____\/--''

Check out our docs on how you can make Korbit work best for you and your team.

Loving Korbit!? Share us on LinkedIn Reddit and X

@gemini-code-assist
Copy link

Summary of Changes

Hello @ioncakephper, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, focuses on enhancing the project's security by resolving two identified vulnerabilities within its yarn dependencies. The primary action involves upgrading the Docusaurus framework components, @docusaurus/core and @docusaurus/preset-classic, to their latest stable versions. This update subsequently triggers a comprehensive refresh of various transitive packages to ensure all known security issues are mitigated.

Highlights

  • Dependency Upgrades: Upgraded @docusaurus/core and @docusaurus/preset-classic from version 3.6.3 to 3.9.0.
  • Vulnerability Fixes: Addressed two identified security vulnerabilities: a high-severity 'Origin Validation Error' and a medium-severity 'Exposed Dangerous Method or Function', both related to webpack-dev-server.
  • Transitive Dependency Updates: Updated numerous underlying yarn dependencies to their latest patched versions to align with the Docusaurus upgrades and resolve transitive security issues.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request from Snyk aims to fix two security vulnerabilities by upgrading Docusaurus dependencies. This is a positive change for the project's security. However, I've found a critical issue in website/package.json where @docusaurus/preset-classic is listed twice. This duplication can cause unpredictable behavior in dependency resolution. I've provided a suggestion to fix this. After applying the fix, please remember to regenerate the yarn.lock file to ensure consistency.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants