[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 automates a critical security update by upgrading the react-markdown library to its latest major version. This change is primarily driven by the need to mitigate a known Regular Expression Denial of Service (ReDoS) vulnerability. The update also involves a significant refresh of the project's dependency graph, bringing many underlying packages to their newer versions to maintain ecosystem health and security.

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 upgrade of react-markdown necessitated a comprehensive update of numerous transitive dependencies, including various @types packages, micromark utilities, mdast utilities, and unist utilities, ensuring compatibility and incorporating newer versions across the dependency tree.

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 from Snyk upgrades react-markdown from v8.0.7 to v9.0.0 to resolve a ReDoS security vulnerability. This is a major version update and introduces breaking changes. The modifications to package.json and package-lock.json are correct for this dependency upgrade. Since this is a major version bump, it's crucial to perform thorough testing to ensure that no regressions are introduced, especially in parts of the application that use react-markdown for rendering content. Key breaking changes in v9 include the removal of props like renderers and allowDangerousHtml, which are replaced by components and the rehype-raw plugin, respectively.