Skip to content

[Snyk] Fix for 2 vulnerabilities#11467

Closed
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-9ef33963643658a1eed98baea258d379
Closed

[Snyk] Fix for 2 vulnerabilities#11467
q1blue wants to merge 1 commit intomasterfrom
snyk-fix-9ef33963643658a1eed98baea258d379

Conversation

@q1blue
Copy link
Copy Markdown
Collaborator

@q1blue q1blue commented Jan 30, 2026

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

  • 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 Directory Traversal
SNYK-JS-TAR-15032660
  149  
medium severity Directory Traversal
SNYK-JS-TAR-15127355
  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:

🦉 Directory Traversal


EntelligenceAI PR Summary

Upgrades Docusaurus framework dependencies from canary build to stable 2.0.1 release for the microsite.

  • Updated @docusaurus/core from version 0.0.0-5591 to 2.0.1
  • Updated @docusaurus/preset-classic from version 0.0.0-5591 to 2.0.1
  • Retained @docusaurus/plugin-client-redirects at pre-release version
  • Represents migration from development build to official stable release
  • Implements phased upgrade approach for documentation framework

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Jan 30, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @q1blue, 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 aims to enhance the project's security posture by automatically applying necessary dependency upgrades. It targets specific vulnerabilities by updating core Docusaurus packages, ensuring the application benefits from the latest security patches. The primary impact is a reduction in security risks associated with outdated dependencies.

Highlights

  • Security Vulnerability Fix: This pull request, automatically generated by Snyk, addresses two Directory Traversal vulnerabilities (SNYK-JS-TAR-15032660 and SNYK-JS-TAR-15127355) found in the project's yarn dependencies.
  • Dependency Upgrades: The @docusaurus/core and @docusaurus/preset-classic dependencies in microsite/package.json have been upgraded from version 0.0.0-5591 to 2.0.1 to resolve the identified vulnerabilities.
  • Yarn Lock File Warning: A warning is present indicating that the yarn.lock file was not updated and requires manual intervention before merging, especially for projects using Yarn's zero-installs feature.
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.

@snyk-io
Copy link
Copy Markdown

snyk-io Bot commented Jan 30, 2026

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

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Copy link
Copy Markdown

@entelligence-ai-pr-reviews entelligence-ai-pr-reviews Bot left a comment

Choose a reason for hiding this comment

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

Walkthrough

This PR upgrades the microsite's Docusaurus framework from a pre-release canary build to the official stable 2.0.1 release. The update affects the core Docusaurus packages and the classic preset, which are fundamental to the documentation site's build and functionality. Notably, the client redirects plugin remains on the pre-release version, indicating a selective upgrade strategy that prioritizes stabilizing the core framework while deferring other components. This migration moves the project from an experimental development build (version 0.0.0-5591) to a production-ready stable release, improving reliability and access to official support.

Changes

File(s) Summary
microsite/package.json Upgraded @docusaurus/core and @docusaurus/preset-classic from pre-release version 0.0.0-5591 to stable version 2.0.1; @docusaurus/plugin-client-redirects remains at pre-release version.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Dev as Developer
    participant PM as Package Manager
    participant Microsite as Microsite Application
    participant Docusaurus as Docusaurus Framework

    Dev->>PM: Update package.json dependencies
    Note over PM: @docusaurus/core: 0.0.0-5591 → 2.0.1<br/>@docusaurus/preset-classic: 0.0.0-5591 → 2.0.1
    Dev->>PM: Run install command
    PM->>Docusaurus: Fetch version 2.0.1 packages
    Docusaurus-->>PM: Return updated packages
    PM->>Microsite: Install new dependencies
    Note over Microsite: Application now uses<br/>Docusaurus 2.0.1
    PM-->>Dev: Dependencies updated successfully
Loading

▶️AI Code Reviews for VS Code, Cursor, Windsurf
Install the extension

Note for Windsurf Please change the default marketplace provider to the following in the windsurf settings:

Marketplace Extension Gallery Service URL: https://marketplace.visualstudio.com/_apis/public/gallery

Marketplace Gallery Item URL: https://marketplace.visualstudio.com/items

Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below

Emoji Descriptions:

  • ⚠️ Potential Issue - May require further investigation.
  • 🔒 Security Vulnerability - Fix to ensure system safety.
  • 💻 Code Improvement - Suggestions to enhance code quality.
  • 🔨 Refactor Suggestion - Recommendations for restructuring code.
  • ℹ️ Others - General comments and information.

Interact with the Bot:

  • Send a message or request using the format:
    @entelligenceai + *your message*
Example: @entelligenceai Can you suggest improvements for this code?
  • Help the Bot learn by providing feedback on its responses.
    @entelligenceai + *feedback*
Example: @entelligenceai Do not comment on `save_auth` function !

Also you can trigger various commands with the bot by doing
@entelligenceai command

The current supported commands are

  1. config - shows the current config
  2. retrigger_review - retriggers the review

More commands to be added soon.

Comment thread microsite/package.json
Comment on lines +32 to +34
"@docusaurus/core": "2.0.1",
"@docusaurus/plugin-client-redirects": "0.0.0-5591",
"@docusaurus/preset-classic": "0.0.0-5591",
"@docusaurus/preset-classic": "2.0.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.

Correctness: ⚠️ Inconsistent Docusaurus versions detected. @docusaurus/core and @docusaurus/preset-classic upgraded to 2.0.1, but @docusaurus/plugin-client-redirects remains at 0.0.0-5591. This version mismatch can cause runtime errors, plugin incompatibility, or build failures. All Docusaurus packages should use compatible versions.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

File: microsite/package.json
Lines: 32-34

Problem: The diff upgrades @docusaurus/core and @docusaurus/preset-classic to version 2.0.1, but leaves @docusaurus/plugin-client-redirects at 0.0.0-5591. This creates a version mismatch that can cause plugin incompatibility or runtime errors.

Fix Instructions:
1. Update @docusaurus/plugin-client-redirects from "0.0.0-5591" to "2.0.1" to match the other Docusaurus packages
2. Verify all Docusaurus-related packages use compatible versions
3. Run `npm install` or `yarn install` to update lockfile
4. Test the build and start scripts to ensure no breaking changes
✨ Committable Code Suggestion

💡 This is a one-click fix! Click "Commit suggestion" to apply this change directly to your branch.

Suggested change
"@docusaurus/core": "2.0.1",
"@docusaurus/plugin-client-redirects": "0.0.0-5591",
"@docusaurus/preset-classic": "0.0.0-5591",
"@docusaurus/preset-classic": "2.0.1",
"yaml-loader": "^0.8.0"
},
"prettier": "@spotify/prettier-config",
"dependencies": {
"@docusaurus/core": "2.0.1",
"@docusaurus/plugin-client-redirects": "2.0.1",
"@docusaurus/preset-classic": "2.0.1",
"@swc/core": "^1.3.46",
"clsx": "^1.1.1",
"docusaurus-plugin-sass": "^0.2.3",

Copy link
Copy Markdown

@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 updates @docusaurus/core and @docusaurus/preset-classic to version 2.0.1 in microsite/package.json to address two reported vulnerabilities. However, the yarn.lock file was not updated, which is a critical issue that needs to be resolved to ensure the new dependency versions are actually used and the vulnerabilities are fixed.

Comment thread microsite/package.json
Comment on lines +32 to +34
"@docusaurus/core": "2.0.1",
"@docusaurus/plugin-client-redirects": "0.0.0-5591",
"@docusaurus/preset-classic": "0.0.0-5591",
"@docusaurus/preset-classic": "2.0.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.

critical

The package.json has been updated to newer versions of @docusaurus/core and @docusaurus/preset-classic. However, the yarn.lock file has not been updated to reflect these changes, as noted in the PR description. This can lead to inconsistent dependency resolution and means the project might still be using the vulnerable versions, or could fail to build. Please run yarn install (or yarn if using Yarn v2+) to regenerate the yarn.lock file and ensure all dependencies are correctly updated.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Feb 6, 2026

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 Feb 6, 2026
@github-actions github-actions Bot closed this Mar 14, 2026
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.

2 participants