Bump @metamask/snaps-controllers from 13.1.0 to 14.0.2

[dependabot]

Bumps @metamask/snaps-controllers from 13.1.0 to 14.0.2.

Commits

• f56d0dd release: 118.0.0 (#3524)
• a47bb43 feat: Add snap_startTrace and snap_endTrace methods for performance traci...
• 9ef5f0f fix: Improve executor error messaging (#3521)
• 71d4834 fix: Ensure Snap gets half of allocated init time (#3522)
• 46c9eb9 chore: Bump @​metamask/utils from 11.4.0 to 11.4.1 (#3516)
• 2786b0e fix: Show different error message for cancelled requests when Snap is stopped...
• 7a1340b feat: Auto grant EVM permissions to preinstalled Snaps (#3410)
• b485691 fix: Clear cronjobs when installing a Snap (#3514)
• 0e13483 ci: Lint changelogs in CI (#3512)
• 6399f71 release: 117.0.0 (#3511)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​metamask/​snaps-utils@​11.0.0
	@​metamask/​snaps-rpc-methods@​13.1.0 ⏵ 13.3.0	-2		-26	-1	-50
	@​metamask/​snaps-controllers@​13.1.0 ⏵ 14.0.2	-4		-26		-50
	@​metamask/​snaps-sdk@​9.1.0

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Block		@metamask/snaps-sdk@9.1.0 has Network access. Module: globalThis["fetch"] Location: Package overview From: package.json → npm/@metamask/snaps-sdk@9.1.0 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/snaps-sdk@9.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		@metamask/snaps-utils@11.0.0 has Network access. Module: globalThis["fetch"] Location: Package overview From: package.json → npm/@metamask/snaps-utils@11.0.0 ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/snaps-utils@11.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[cursor]

Bug: Snap SDK Update Causes Dependency Conflicts

Updating @metamask/snaps-controllers to ^14.0.2 in devDependencies introduces version conflicts. It requires @metamask/snaps-sdk@^9.1.0, @metamask/snaps-utils@^11.0.0, and @metamask/utils@^11.4.1, which are newer than the currently specified ^8.1.0, ^10.1.0, and ^11.4.0 respectively. This mismatch results in multiple major versions of these packages being installed, leading to dependency resolution issues and potential runtime inconsistencies.

package.json#L45-L48

snaps-registry/package.json

Lines 45 to 48 in 5227b61

	"@metamask/eslint-config-typescript": "^12.1.0",
	"@metamask/snaps-controllers": "^14.0.2",
	"@metamask/snaps-sdk": "^8.1.0",
	"@metamask/snaps-utils": "^10.1.0",

Fix in Cursor

---

Was this report helpful? Give feedback by reacting with 👍 or 👎

[dependabot]

Superseded by #1276.