chore: bump runtime deps

[legobeat]

non-breaking bumps of runtime dependencies

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@cypress/request@3.0.1	environment, filesystem, network	+5	329 kB	cypress-npm-publisher
npm/@metamask/eth-json-rpc-infura@9.1.0	None	+2	92.9 kB	mcmire
npm/@metamask/eth-json-rpc-middleware@12.1.0	network	+4	266 kB	metamaskbot
npm/@metamask/eth-sig-util@7.0.1	None	+2	513 kB	metamaskbot
npm/@metamask/rpc-errors@6.2.1	None	0	129 kB	metamaskbot
npm/@metamask/utils@8.4.0	None	+9	1.73 MB	metamaskbot
npm/@noble/curves@1.3.0	None	+1	2.15 MB	paulmillr
npm/@scure/base@1.1.6	None	0	80.4 kB	paulmillr
npm/call-bind@1.0.7	None	+4	68.7 kB	ljharb
npm/define-data-property@1.1.4	None	+3	62.7 kB	ljharb
npm/ethereum-cryptography@2.1.3	None	+2	517 kB	paulmillr
npm/function-bind@1.1.2	None	0	31.4 kB	ljharb
npm/get-intrinsic@1.2.4	eval	+3	69.9 kB	ljharb
npm/has-property-descriptors@1.0.2	None	+1	22.7 kB	ljharb
npm/json-stable-stringify@1.1.1	None	+1	47.1 kB	ljharb
npm/node-fetch@2.7.0	network	+3	493 kB	node-fetch-bot

🚮 Removed packages: npm/@cypress/request@3.0.0, npm/@metamask/eth-json-rpc-infura@9.0.0, npm/@metamask/eth-json-rpc-middleware@12.0.0, npm/@metamask/eth-sig-util@7.0.0, npm/@metamask/rpc-errors@6.1.0, npm/@metamask/utils@8.1.0, npm/@noble/curves@1.1.0, npm/@noble/hashes@1.3.2, npm/define-data-property@1.1.1, npm/ethereum-cryptography@2.1.2, npm/get-intrinsic@1.2.1

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-infura@9.1.0, npm/@metamask/safe-event-emitter@3.1.1, npm/jsonify@0.0.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/jsonify@0.0.1
@SocketSecurity ignore npm/@metamask/eth-json-rpc-infura@9.1.0
@SocketSecurity ignore npm/@metamask/safe-event-emitter@3.1.1

new authors ok

[Gudahtt]

LGTM!