Skip to content

[Snyk] Fix for 1 vulnerabilities#231

Open
prma85 wants to merge 1 commit intomasterfrom
snyk-fix-969c634fdcc18a737414418d91233960
Open

[Snyk] Fix for 1 vulnerabilities#231
prma85 wants to merge 1 commit intomasterfrom
snyk-fix-969c634fdcc18a737414418d91233960

Conversation

@prma85
Copy link
Owner

@prma85 prma85 commented Feb 12, 2026

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):

  • website/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
high severity Prototype Pollution
SNYK-JS-AXIOS-15252993
  828  

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:

🦉 Prototype Pollution


Note

Medium Risk
Major-version dependency upgrade that can introduce breaking changes in the docs site build/runtime. The lockfile does not appear updated, which may cause inconsistent installs in CI or for developers.

Overview
Upgrades the website’s Docusaurus dependencies by bumping @docusaurus/core and @docusaurus/preset-classic from ^2.3.1 to ^3.0.0 to address a reported vulnerability.

Written by Cursor Bugbot for commit 492edb2. This will update automatically on new commits. Configure here.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

"@docusaurus/core": "^2.3.1",
"@docusaurus/preset-classic": "^2.3.1",
"@docusaurus/core": "^3.0.0",
"@docusaurus/preset-classic": "^3.0.0",
Copy link

Choose a reason for hiding this comment

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

React 16 incompatible with Docusaurus v3 upgrade

High Severity

Upgrading @docusaurus/core and @docusaurus/preset-classic from v2 to ^3.0.0 requires React 18+, but react and react-dom remain pinned at ^16.14.0. Docusaurus v3 has a peer dependency on react >= 18, so this will fail to install (peer dependency conflict) or fail at runtime. Both react and react-dom need to be upgraded to ^18.0.0 as part of this major version bump.

Additional Locations (1)

Fix in Cursor Fix in Web

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.

2 participants