[Snyk] Upgrade @modelcontextprotocol/sdk from 1.18.0 to 1.25.1

[iamdrewfortini]

Snyk has created this PR to upgrade @modelcontextprotocol/sdk from 1.18.0 to 1.25.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 19 versions ahead of your current version.

• The recommended version was released 25 days ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Insecure Default Initialization of Resource SNYK-JS-MODELCONTEXTPROTOCOLSDK-14171914	161	No Known Exploit

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gemini-code-assist]

Summary of Changes

Hello @iamdrewfortini, 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 @modelcontextprotocol/sdk dependency to its latest recommended version. The primary goal of this update is to patch a critical security vulnerability, ensuring the project benefits from the most recent security enhancements and stability improvements.

Highlights

• Dependency Upgrade: Upgraded the @modelcontextprotocol/sdk dependency from version 1.18.0 to 1.25.1.
• Security Fix: This upgrade addresses a high-severity vulnerability, SNYK-JS-MODELCONTEXTPROTOCOLSDK-14171914 (Insecure Default Initialization of Resource), which has a score of 161.

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
	@​modelcontextprotocol/​sdk@​1.18.0 ⏵ 1.25.2		+22

View full report

[gemini-code-assist]

Code Review

This pull request from Snyk upgrades @modelcontextprotocol/sdk to fix a high-severity security vulnerability. While the update to package.json is correct, the PR is critically flawed because it's missing the corresponding update to pnpm-lock.yaml. This omission means the vulnerability might not be fixed in all environments, as builds will not be deterministic. The lock file must be updated and included in this PR.

[gemini-code-assist]

The pnpm-lock.yaml file is missing from this pull request. When updating dependencies in a project using pnpm, the lock file must be committed along with package.json to ensure that all developers and CI/CD pipelines use the exact same dependency versions. Without the updated lock file, the security vulnerability this PR aims to fix may persist in some environments.

Please run pnpm install to generate the updated pnpm-lock.yaml and add it to this pull request.