chore(deps-dev): bump @metamask/snaps-cli from 6.2.1 to 7.1.0

[dependabot]

Bumps @metamask/snaps-cli from 6.2.1 to 7.1.0.

Release notes

Sourced from @​metamask/snaps-cli's releases.

7.0.0

@​metamask/rpc-methods 0.38.2-flask.1

Changed

• Remove business-logic callbacks from manageAccounts (#1725)
• Bump @metamask/utils and @metamask/snaps-registry (#1694)

@​metamask/snaps-controllers 0.38.3-flask.1

Changed

• Bump @metamask/post-message-stream from 6.1.2 to 7.0.0 (#1707, #1724)
• Bump @metamask/utils and @metamask/snaps-registry (#1694)

Fixed

• Fix unpacking zero byte files from NPM (#1708)

@​metamask/snaps-execution-environments 0.38.3-flask.1

Changed

• Bump @metamask/post-message-stream from 6.1.2 to 7.0.0 (#1707, #1724)
• Bump @metamask/utils and @metamask/snaps-registry (#1694)

Fixed

• Add hardening for Request, Headers, and Response endowments (#1695)

@​metamask/snaps-utils 0.38.3-flask.1

Changed

• Bump @metamask/post-message-stream from 6.1.2 to 7.0.0 (#1707, #1724)
• Bump @metamask/utils and @metamask/snaps-registry (#1694)

Commits

• d6d1729 Release 102.0.0 (#3345)
• 81c33fd feat: Add snaps-sandbox package and integrate into CLI (#3306)
• 0c476de perf: Use typedUnion for UserInputEventStruct (#3344)
• 18e4993 fix: Increase boot request queue limit (#3340)
• b9e7f41 chore(deps): bump @​metamask/providers from 21.0.0 to 22.0.0 (#3336)
• b39662b chore(deps-dev): bump @​metamask/create-release-branch from 4.1.1 to 4.1.2 (#3...
• a4afb6c chore(deps): bump @​metamask/eth-json-rpc-middleware from 16.0.1 to 17.0.0 (#3...
• b1dcaa5 chore(deps): bump http-proxy-middleware from 2.0.7 to 2.0.9 in the npm_and_ya...
• 60ada40 chore(deps): bump @​metamask/utils from 11.2.0 to 11.3.0 (#3232)
• 8cf11b2 release: 101.0.0 (#3333)
• 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-cli@​6.7.0 ⏵ 7.1.0	+2			+2

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		accepts@2.0.0 has a New author. New Author: wesleytodd Previous Author: dougwilson Source: packages/snap/package.json ℹ Read more on: This package | This alert | What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/accepts@2.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.
Block		content-disposition@1.0.0 has a New author. New Author: wesleytodd Previous Author: dougwilson Source: packages/snap/package.json ℹ Read more on: This package | This alert | What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/content-disposition@1.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.
Block		mime-types@3.0.1 has a New author. New Author: ulisesgascon Previous Author: wesleytodd Source: packages/snap/package.json ℹ Read more on: This package | This alert | What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/mime-types@3.0.1. 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		negotiator@1.0.0 has a New author. New Author: wesleytodd Previous Author: dougwilson Source: packages/snap/package.json ℹ Read more on: This package | This alert | What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/negotiator@1.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.
Block		type-is@2.0.1 has a New author. New Author: ulisesgascon Previous Author: wesleytodd Source: packages/snap/package.json ℹ Read more on: This package | This alert | What is new author? 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: Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/type-is@2.0.1. 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

[dependabot]

Superseded by #195.