search

MetaMask / eth-json-rpc-filters

json-rpc-engine middleware implementing ethereum filter methods
ISC License
29 stars 38 forks source link

Bump @metamask/eth-json-rpc-provider from 2.3.1 to 2.3.2 #138

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 7 months ago

Bumps @metamask/eth-json-rpc-provider from 2.3.1 to 2.3.2.

Commits
  • b20eb08 Release 111.0.0 (#3821)
  • f4b889a chore(deps-dev): bump @​metamask/create-release-branch from 2.0.1 to 3.0.0 (#3...
  • 2c97df2 chore(user-operation-controller): Remove unnecessary peerDependency (#3823)
  • 7b139dc feat: Keep PreferencesController in sync with keyring state (#3799)
  • 007648b Release/110.0.0 (#3810)
  • de3dc1a Move keyring-controller dep to devdep in Accounts Controller (#3820)
  • ef35512 refactor: Remove duplicated code in setProviderType (#3813)
  • ed8423e refactor: Remove usage of deprecated setProviderType (#3807)
  • 028b711 chore(network-controller): Remove unused internal variable (#3811)
  • 72424ec chore(deps): bump @​metamask/eth-keyring-controller from 17.0.0 to 17.0.1 (#3805)
  • Additional commits viewable in compare view


Dependabot compatibility score

You can trigger a rebase of this PR 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 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)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

socket-security[bot] commented 7 months ago

🚨 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 NoteSource
Unpublished package npm/@metamask/json-rpc-engine@7.3.2
  • Version: 7/3/2002, 12:00:00 AM
Unpublished package npm/@metamask/eth-json-rpc-provider@2.3.2
  • Version: 2/3/2002, 12:00:00 AM

View full report↗︎

Next steps

What are unpublished packages?

Package version was not found on the registry. It may exist on a different registry and need to be configured to pull from that registry.

Packages can be removed from the registry by manually un-publishing, a security issue removal, or may simply never have been published to the registry. Reliance on these packages will cause problem when they are not found.

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/json-rpc-engine@7.3.2
  • @SocketSecurity ignore npm/@metamask/eth-json-rpc-provider@2.3.2
dependabot[bot] commented 1 month ago

Superseded by #185.