Bump @metamask/providers from 13.0.0 to 14.0.2

[dependabot]

Bumps @metamask/providers from 13.0.0 to 14.0.2.

Release notes

Sourced from @​metamask/providers's releases.

14.0.2

Fixed

• Don't send null params to underlying provider (#292)

14.0.1

Fixed

• Don't send undefined params to underlying provider (#290)

14.0.0

Changed

• BREAKING: Update to streams3 API (#288)
  • Update extension-port-stream from ^2.1.1 to ^3.0.0
    • Force subdependency readable-stream to ^3.6.2 in resolutions
  • Update json-rpc-middleware-stream from ^4.2.3 to ^5.0.1
  • Update @metamask/object-multiplex from ^1.3.0 to ^2.0.0
  • Add direct dependency on readable-stream@^3.6.2
  • Replace internal usage of stream with readable-stream

13.1.0

Added

• Add support for EIP-6963 (#263)
  • initializeProvider() params object now accepts an optional providerInfo property with a value of EIP6963ProviderInfo object
  • Add eip6963AnnounceProvider() which supports a wallet by announcing a provider through the eip6963:announceProvider event and re-announcing the provider whenever an eip6963:requestProvider event is received
  • Add eip6963RequestProvider() which supports a dapp by dispatching an eip6963:requestProvider event and invoking a callback for each eip6963:announceProvider event received
  • Add EIP6963AnnounceProviderEvent type
  • Add EIP6963ProviderDetail type
  • Add EIP6963ProviderInfo type
  • Add EIP6963RequestProviderEvent type

Changelog

Sourced from @​metamask/providers's changelog.

[14.0.2]

Fixed

• Don't send null params to underlying provider (#292)

[14.0.1]

Fixed

• Don't send undefined params to underlying provider (#290)

[14.0.0]

Changed

• BREAKING: Update to streams3 API (#288)
  • Update extension-port-stream from ^2.1.1 to ^3.0.0
    • Force subdependency readable-stream to ^3.6.2 in resolutions
  • Update json-rpc-middleware-stream from ^4.2.3 to ^5.0.1
  • Update @metamask/object-multiplex from ^1.3.0 to ^2.0.0
  • Add direct dependency on readable-stream@^3.6.2
  • Replace internal usage of stream with readable-stream

[13.1.0]

Added

• Add support for EIP-6963 (#263)
  • initializeProvider() params object now accepts an optional providerInfo property with a value of EIP6963ProviderInfo object
  • Add eip6963AnnounceProvider() which supports a wallet by announcing a provider through the eip6963:announceProvider event and re-announcing the provider whenever an eip6963:requestProvider event is received
  • Add eip6963RequestProvider() which supports a dapp by dispatching an eip6963:requestProvider event and invoking a callback for each eip6963:announceProvider event received
  • Add EIP6963AnnounceProviderEvent type
  • Add EIP6963ProviderDetail type
  • Add EIP6963ProviderInfo type
  • Add EIP6963RequestProviderEvent type

Commits

• 126a8c8 14.0.2 (#293)
• b3d0506 Strip params if null is passed (#292)
• f10765d 14.0.1 (#291)
• d5d5de4 Don't send undefined params (#290)
• ae74a05 14.0.0 (#289)
• 024925d deps: Update to streams3 API (#288)
• 26a9040 Bump @​babel/traverse from 7.21.4 to 7.23.2 (#287)
• 7342303 13.1.0 (#286)
• 215ae38 Implement EIP-6963 (#263)
• 8a95e40 Bump postcss from 8.4.23 to 8.4.31 (#285)
• 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]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@metamask/providers	13.0.0...14.0.2	None	+9/-5	927 kB	metamaskbot

[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.

Issue	Package	Version	Note	Source
New author	extension-port-stream	3.0.0	New Author: lgbot Previous Author: gudahtt	@metamask/providers@14.0.2 via package.json

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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore extension-port-stream@3.0.0

[dependabot]

Superseded by #108.