deps: @metamask/json-rpc-engine@^7.1.0->^8.0.2

[legobeat]

Bump @metamask/json-rpc-engine from v7 to v8.

Related

• 12.1.2 eth-json-rpc-middleware#308 enables removing v7 as devDependency as well.

Blocking

• BREAKING: drop support for Node.js v16, v21 #164

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/eth-block-tracker@9.0.3	None	+1	140 kB	lgbot
npm/@metamask/eth-json-rpc-middleware@12.1.1	network	+11	1.31 MB	lgbot
npm/@metamask/json-rpc-engine@8.0.2	None	0	189 kB	metamaskbot
npm/@metamask/rpc-errors@6.3.0	None	+1	167 kB	metamaskbot
npm/@metamask/safe-event-emitter@3.1.1	None	0	24.1 kB	lgbot
npm/@metamask/utils@8.5.0	Transitive: network	+11	2.19 MB	metamaskbot
npm/@scure/base@1.1.6	None	0	80.4 kB	paulmillr

🚮 Removed packages: npm/@metamask/eth-json-rpc-middleware@12.0.1, npm/@metamask/json-rpc-engine@7.3.1, npm/@metamask/rpc-errors@6.1.0, npm/@metamask/safe-event-emitter@3.0.0, npm/@metamask/utils@8.2.1, npm/@scure/base@1.1.3, npm/eth-block-tracker@8.0.0

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/@metamask/eth-json-rpc-middleware@12.1.1, npm/@metamask/safe-event-emitter@3.1.1

View full report↗︎

Next steps

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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[legobeat]

@SocketSecurity ignore npm/@metamask/eth-json-rpc-middleware@12.0.1
@SocketSecurity ignore npm/@metamask/eth-json-rpc-middleware@12.1.1

network access ok (note: in reality only the latter is used)

[legobeat]

@SocketSecurity ignore npm/@metamask/safe-event-emitter@3.0.0
@SocketSecurity ignore npm/@metamask/safe-event-emitter@3.1.1

new author ok (note: in reality only the latter is used)

[MajorLift]

LGTM! Clicked the merge button by mistake, sorry about that.