[Snyk] Security upgrade mermaid from 11.5.0 to 11.12.1

[arthrod]

Snyk has created this PR to fix 1 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
	Prototype Pollution SNYK-JS-DAGRED3ES-13110069	708

---

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

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[gemini-code-assist]

Summary of Changes

Hello @arthrod, 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, automatically generated by Snyk, updates the mermaid package to a newer version to resolve a critical security vulnerability related to Prototype Pollution. The change ensures the project's dependencies are secure by bringing mermaid and its associated sub-dependencies up to date.

Highlights

• Security Upgrade: This pull request performs a security upgrade for the mermaid dependency from version 11.5.0 to 11.12.1.
• Vulnerability Fixed: The upgrade addresses a 'Prototype Pollution' vulnerability (SNYK-JS-DAGRED3ES-13110069) with a severity score of 708.
• Dependency Updates: The package.json and package-lock.json files have been updated to reflect the new mermaid version and several transitive dependencies, including @antfu/install-pkg, @antfu/utils, @iconify/utils, dagre-d3-es, dayjs, dompurify, exsolve, katex, langium, marked, package-manager-detector, quansync, and tinyexec.

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

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-1b60b1fe5fcbc4f374d30fa9c2d58565

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades the mermaid package to version 11.12.1 to resolve a security vulnerability. While this is a necessary update, it's important to note that it also updates several transitive dependencies. One of these, marked, is updated to a version that requires Node.js 20 or higher. Your project currently supports Node.js 18, which could lead to compatibility issues. I've added a specific comment highlighting this potential problem.

[gemini-code-assist]

The marked package, a transitive dependency of mermaid, has been updated to a version that requires Node.js 20 or higher. Your project's package.json specifies a Node.js version range of >=18.13.0 <=22.x.x, which could lead to compatibility issues in environments running Node.js 18. It is recommended to either update your project's Node.js requirement to >=20 or use npm overrides to force a compatible version of marked for mermaid.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Align engine support with mermaid's Node 20 dependency

The upgrade to mermaid@11.12.1 pulls in marked@16.4.2, which declares an engine requirement of node >= 20 (package-lock.json lines 8033‑8043). The project still advertises support for Node >=18.13 in package.json, so developers following the documented minimum will hit engine errors (pnpm/engine‑strict) or run code compiled for newer runtime features. Either raise the documented Node requirement to 20 or stay on a mermaid release whose transitive dependencies still support Node 18.

Useful? React with 👍 / 👎.

[openhands-ai]

Looks like there are a few issues preventing this PR from being merged!

• GitHub Actions are failing:
  • Integration Test

If you'd like me to help, just leave a comment, like

@OpenHands please fix the failing actions on PR #89 at branch `snyk-fix-1b60b1fe5fcbc4f374d30fa9c2d58565`

Feel free to include any additional details that might help me get this PR into a better state.

_{^{You can manage your notification settings}}