[Snyk] Security upgrade solana-agent-kit from 1.3.4 to 2.0.1

[SMSDAO]

Snyk has created this PR to fix 2 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

• examples/discord-bot-starter/package.json
• examples/discord-bot-starter/pnpm-lock.yaml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Prototype Pollution SNYK-JS-AXIOS-15252993	828
	Server-side Request Forgery (SSRF) SNYK-JS-LANGCHAINCORE-15268429	541

---

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
🦉 Server-side Request Forgery (SSRF)

[Copilot]

Pull request overview

This PR updates the examples/discord-bot-starter dependency on solana-agent-kit to address Snyk-reported vulnerabilities (prototype pollution via axios and SSRF via langchain/core) by upgrading to the 2.x release line.

Changes:

• Bump solana-agent-kit in the Discord bot starter example.
• Update pnpm-lock.yaml to the new resolved dependency graph.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 2 comments.

File	Description
examples/discord-bot-starter/package.json	Updates the declared solana-agent-kit dependency range.
examples/discord-bot-starter/pnpm-lock.yaml	Updates lockfile resolutions for solana-agent-kit and its transitive deps.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

package.json now declares solana-agent-kit: ^2.0.1, but the updated pnpm-lock.yaml resolves solana-agent-kit to 2.0.10 and even records the specifier as ^2.0.10. Please align these (either update package.json to ^2.0.10 / regenerate the lockfile from this package.json, or pin to 2.0.1 if that exact version is required) so installs are reproducible and CI doesn’t report an out-of-date lockfile.

Suggested change

	"solana-agent-kit": "^2.0.1"
	"solana-agent-kit": "^2.0.10"

[Copilot]

The lockfile records solana-agent-kit with specifier: ^2.0.10 while package.json declares ^2.0.1. These should match; otherwise pnpm will treat the lockfile as stale and update it during install. Regenerate the lockfile after aligning the dependency range, or update package.json to the same range used here.

Suggested change

	specifier: ^2.0.10
	specifier: ^2.0.1