[Snyk] Security upgrade react-markdown from 8.0.7 to 9.0.0

[q1blue]

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

Snyk changed the following file(s):

• gui/package.json
• gui/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	62

---

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 pull request performs an automated security upgrade of the react-markdown library to mitigate a critical Regular Expression Denial of Service (ReDoS) vulnerability. The update ensures the application uses a more secure version of the markdown parsing library, enhancing overall system stability and resilience against malicious inputs.

Highlights

• Security Upgrade: The react-markdown package has been upgraded from version 8.0.7 to 9.0.0 to address a Regular Expression Denial of Service (ReDoS) vulnerability (SNYK-JS-DIFF-14917201).
• Dependency Updates: This major version bump of react-markdown has led to a significant cascade of updates and additions across its transitive dependencies, including various @types packages, micromark related utilities, and unified ecosystem packages.

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

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades react-markdown from version 8.0.7 to 9.0.0 to fix a security vulnerability (ReDoS). While this is an important security update, upgrading to a new major version of react-markdown introduces significant breaking changes. The current PR only updates the package versions and does not include the necessary code modifications to adapt to the new API. This will likely lead to runtime errors. I've added a critical comment on package.json detailing the issue and recommending that the code using react-markdown be updated before this PR is merged.

[gemini-code-assist]

Upgrading react-markdown from version 8 to 9 is a major update that introduces significant breaking changes. The application code using this library needs to be updated to avoid runtime errors.

Some of the key breaking changes include:

• The plugins prop is removed. Use remarkPlugins and rehypePlugins instead.
• The renderers prop is removed. Use components instead.
• The allowDangerousHtml and escapeHtml props are removed. To render HTML, you now need to use the rehype-raw plugin.
• The source prop is removed. Use children instead.

Since this PR only updates the dependency version without the necessary code changes, merging it as is will likely break the application. Please find all usages of <ReactMarkdown> in the codebase and update them according to the v9 migration guide.