[Snyk] Security upgrade @dynamic-labs/sdk-react from 0.17.25 to 0.18.30

[q1blue]

Snyk has created this PR to fix 5 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
	Denial of Service (DoS) SNYK-JS-WS-7266574	160
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BABELRUNTIME-10044504	140
	Prototype Pollution SNYK-JS-LODASH-15053838	87
	Prototype Pollution SNYK-JS-LODASHES-15053836	87
	Uncontrolled Recursion SNYK-JS-ESLINT-15102420	45

---

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)
🦉 Prototype Pollution

[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 upgrade for the @dynamic-labs/sdk-react dependency. The update is essential for mitigating multiple identified vulnerabilities, thereby strengthening the project's security posture and reducing potential risks associated with outdated packages.

Highlights

• Dependency Upgrade: The @dynamic-labs/sdk-react dependency has been upgraded from version 0.17.25 to 0.18.30.
• Security Vulnerability Fixes: This upgrade addresses 5 identified vulnerabilities, including a High severity Denial of Service (DoS) and several Medium severity issues such as Regular Expression Denial of Service (ReDoS), Prototype Pollution, and Uncontrolled Recursion.

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 the @dynamic-labs/sdk-react package from version 0.17.25 to 0.18.30. This is an important security update that resolves 5 vulnerabilities, including one high-severity Denial of Service (DoS) issue. The change is correct and necessary. I've added one suggestion to improve future maintainability by using a caret (^) for the dependency version, which is consistent with most other dependencies in your package.json.

[gemini-code-assist]

To maintain consistency with other dependencies in this project and to allow for automatic non-breaking updates in the future, it would be beneficial to use a caret (^) for this package's version. This will enable npm to fetch patches and minor releases that might include further security fixes or bug fixes without needing a new pull request.

Suggested change

	"@dynamic-labs/sdk-react": "0.18.30",
	"@dynamic-labs/sdk-react": "^0.18.30",