build(deps-dev): bump @metamask/eth-json-rpc-middleware from 15.0.0 to 15.1.0

[dependabot]

Bumps @metamask/eth-json-rpc-middleware from 15.0.0 to 15.1.0.

Release notes

Sourced from @​metamask/eth-json-rpc-middleware's releases.

15.1.0

Changed

• Improved validation of primary type for signTypedDataV3 and signTypedDataV4 (#350)

15.0.1

Changed

• Bump @metamask/eth-block-tracker from ^11.0.1 to ^11.0.3 (#347)

Changelog

Sourced from @​metamask/eth-json-rpc-middleware's changelog.

[15.1.0]

Changed

• Improved validation of primary type for signTypedDataV3 and signTypedDataV4 (#350)

[15.0.1]

Changed

• Bump @metamask/eth-block-tracker from ^11.0.1 to ^11.0.3 (#347)

Commits

• 9db63df 15.1.0 (#352)
• 126626d fix: Add validation for types sign message primary type (#350)
• 4de470d 15.0.1 (#348)
• 3d7246a chore(deps): bump @metamask/eth-block-tracker to ^11.0.3 (#347)
• bf4fe73 Bump micromatch from 4.0.5 to 4.0.8 in the npm_and_yarn group (#343)
• See full diff 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]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/[email protected]	None	+1	790 kB	gudahtt
npm/@metamask/[email protected]	network	+1	882 kB	metamaskbot

🚮 Removed packages: npm/@metamask/[email protected], npm/@metamask/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
New author	npm/@metamask/[email protected]	New Author: gudahtt Previous Author: mcmire	package.json yarn.lock	🚫
Unstable ownership	npm/@metamask/[email protected]	Author: gudahtt	package.json yarn.lock	🚫

View full report↗︎

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

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.

What is unstable ownership?

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@metamask/[email protected]

[dependabot]

Superseded by #209.