[Snyk] Fix for 2 vulnerabilities

[q1blue]

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-TRIM-1017038	169
	Regular Expression Denial of Service (ReDoS) SNYK-JS-OCTOKITREQUEST-8730853	67

---

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:

🦉 Regular Expression Denial of Service (ReDoS)

[gemini-code-assist]

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist¹! 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 automated pull request, generated by Snyk, aims to enhance the project's security posture by updating key dependencies. The changes specifically target and resolve identified Regular Expression Denial of Service (ReDoS) vulnerabilities, ensuring a more robust and secure application environment.

Highlights

• Dependency Upgrades: Upgraded @docusaurus/preset-classic from ^2.4.1 to ^3.0.0 and octokit from ^2.0.14 to ^3.0.0. These updates address two Regular Expression Denial of Service (ReDoS) vulnerabilities.
• Vulnerability Fixes: This pull request fixes two Regular Expression Denial of Service (ReDoS) vulnerabilities: SNYK-JS-TRIM-1017038 (high severity) and SNYK-JS-OCTOKITREQUEST-8730853 (medium severity).

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. ↩

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​docusaurus/​preset-classic@​2.4.1 ⏵ 3.0.0				+1

View full report

[socket-security]

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 "▶" to expand/collapse)
Warn		License policy violation: npm caniuse-lite under CC-BY-4.0 License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (npm metadata) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/LICENSE) License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/package.json) From: package-lock.json → npm/@svgr/webpack@6.5.1 → npm/@docusaurus/preset-classic@3.0.0 → npm/@docusaurus/core@2.4.1 → npm/@docusaurus/plugin-content-docs@2.4.1 → npm/caniuse-lite@1.0.30001766 ℹ 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.30001766. 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		Obfuscated code: npm html-minifier-terser is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: package-lock.json → npm/@docusaurus/preset-classic@3.0.0 → npm/html-minifier-terser@7.2.0 ℹ Read more on: This package | This alert | What is obfuscated code? 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: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/html-minifier-terser@7.2.0. 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

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, aims to fix two security vulnerabilities by upgrading @docusaurus/preset-classic and octokit. However, these upgrades are major version bumps (v2 to v3) and introduce breaking changes. The PR is incomplete as it doesn't update peer dependencies like React and other Docusaurus packages, which will almost certainly cause the build to fail. I've left a critical comment on package.json detailing the required additional dependency updates for the Docusaurus v3 migration. It's crucial to address these issues to ensure the project remains functional after merging. I've also noted that the octokit upgrade will likely require code changes to adapt to its v3 API.

[gemini-code-assist]

This automated dependency upgrade is incomplete and will likely break your project. Upgrading @docusaurus/preset-classic to v3 and octokit to v3 are major version changes that introduce breaking changes.

Docusaurus v3 Upgrade Issues:
The upgrade to @docusaurus/preset-classic v3 requires several other dependencies to be updated in unison. Without these, your build will fail.

• React Version: Docusaurus v3 requires React 18. You need to upgrade react and react-dom from ^17.0.1 to ^18.0.0 (e.g., ^18.2.0).
• Docusaurus Packages: All @docusaurus/* packages must be on the same major version. The following packages also need to be upgraded to ^3.0.0:
  • @docusaurus/core
  • @docusaurus/plugin-content-docs
  • @docusaurus/plugin-google-gtag
  • @docusaurus/plugin-ideal-image
  • @docusaurus/module-type-aliases (in devDependencies)
• MDX Version: Docusaurus v3 uses MDX v3. You need to upgrade @mdx-js/react from ^1.6.22 to ^3.0.0.

Octokit v3 Upgrade:
The upgrade of octokit from v2 to v3 is also a major version change. Please review the octokit v3 release notes for breaking changes and update any code that uses it to ensure compatibility.

It is strongly recommended to either revert this PR and perform the major version upgrades manually while addressing all breaking changes, or update this PR to include all the necessary dependency changes to ensure the project remains functional.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	crystal-alchemist-blue-block-1596	fbf36d4	Jan 27 2026, 12:28 AM

[entelligence-ai-pr-reviews]

Entelligence AI Vulnerability Scanner

Status: No security vulnerabilities found

Your code passed our comprehensive security analysis.