adapt to eip-1193 provider changes

[cryptodev-2s]

Following the update to SafeEventEmitterProvider to support EIP-1193, please note the following changes in the PR:

• The use of sendAsync is being deprecated; we should now use request instead.
  • This change is reflected in the PPOMController.
  • Additionally, several tests that pass a mock provider to the controller have been updated to mock request instead of sendAsync to match the new type requirements.

• Fixes #180

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/json-rpc-engine@9.0.0	None	+1	196 kB	metamaskbot
npm/@metamask/network-controller@20.0.0	environment Transitive: filesystem, network	+49	8.42 MB	metamaskbot
npm/@metamask/rpc-errors@6.3.1	Transitive: network	+13	2.36 MB	metamaskbot
npm/@noble/hashes@1.4.0	None	0	773 kB	paulmillr
npm/tslib@2.6.3	None	0	84.9 kB	typescript-bot

🚮 Removed packages: npm/@metamask/network-controller@17.2.0, npm/@metamask/rpc-errors@6.1.0, npm/tslib@2.6.2

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/eth-json-rpc-infura@9.1.0	New Author: mcmire Previous Author: gudahtt	package.json	🚫
New author	npm/@spruceid/siwe-parser@2.1.0	New Author: sbihel Previous Author: w4ll3	package.json	🚫

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.

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

• @SocketSecurity ignore npm/@metamask/eth-json-rpc-infura@9.1.0
• @SocketSecurity ignore npm/@spruceid/siwe-parser@2.1.0

[mcmire]

This looks good, I just had one comment.

[mcmire]

LGTM!