search

MetaMask / KeyringController

A module for managing groups of Ethereum accounts and using them.
ISC License
229 stars 134 forks source link

chore(deps): bump @metamask/keyring-api from 3.0.0 to 6.4.0 #391

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps @metamask/keyring-api from 3.0.0 to 6.4.0.

Release notes

Sourced from @​metamask/keyring-api's releases.

6.4.0

Changed

  • Add support for @metamask/providers v17 (#329).

6.3.1

Fixed

  • Export Caip* types used in the API (#325).

6.3.0

Added

  • Add getAccountBalances method to Keyring interface (#320).
  • Add CAIP-19 types to utils (#321).

Changed

  • Bump @​metamask/snaps-sdk from 4.2.0 to 4.3.0 (#323).
  • Split api.ts into different files (#319).
  • Make the KeyringAccount type less rigid (#311).

Fixed

  • Ensure that errors are JSON-serializable (#162).
  • Don't use internal types in the public API (#312).
  • Keep all ETH methods in the same enum (#313).

6.2.1

Changed

  • Bump @​metamask/key-tree from 9.1.0 to 9.1.1 (#310).

Fixed

  • Use internal object function instead of the upstream one (#316).

6.2.0

Added

  • Add accountNameSuggestion field to the AccountCreatedEvent (#291)
  • Add displayConfirmation field to the AccountCreatedEvent (#307)

6.1.1

Changed

  • Fix isEvmAccountType accountType type to string or InternalAccountType (#304)
  • Bump @​metamask/snaps-sdk from ^4.0.0 to ^4.2.0 (#305)

6.1.0

Added

  • Add isEvmAccountType helper (#297)
  • Add bip121:p2wpkh account support (#294)

Changed

  • Remove incorrect SignTransaction from EthErc4337Account (#300)
  • Bump @​metamask/providers from 16.0.0 to 16.1.0 (#298)
  • Bump @​metamask/snaps-sdk from 4.0.0 to 4.0.1 (#292)
  • Split account types (EOA + Erc4337) (#293)

... (truncated)

Changelog

Sourced from @​metamask/keyring-api's changelog.

[6.4.0]

Changed

  • Add support for @metamask/providers v17 (#329).

[6.3.1]

Fixed

  • Export Caip* types used in the API (#325).

[6.3.0]

Added

  • Add getAccountBalances method to Keyring interface (#320).
  • Add CAIP-19 types to utils (#321).

Changed

  • Bump @​metamask/snaps-sdk from 4.2.0 to 4.3.0 (#323).
  • Split api.ts into different files (#319).
  • Make the KeyringAccount type less rigid (#311).

Fixed

  • Ensure that errors are JSON-serializable (#162).
  • Don't use internal types in the public API (#312).
  • Keep all ETH methods in the same enum (#313).

[6.2.1]

Changed

  • Bump @​metamask/key-tree from 9.1.0 to 9.1.1 (#310).

Fixed

  • Use internal object function instead of the upstream one (#316).

[6.2.0]

Added

  • Add accountNameSuggestion field to the AccountCreatedEvent (#291)
  • Add displayConfirmation field to the AccountCreatedEvent (#307)

[6.1.1]

... (truncated)

Commits


Dependabot compatibility score

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 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[bot] commented 1 month ago

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

Package New capabilities Transitives Size Publisher
npm/@metamask/json-rpc-engine@8.0.2 None 0 189 kB metamaskbot
npm/@metamask/json-rpc-middleware-stream@7.0.2 None 0 78.4 kB metamaskbot
npm/@metamask/keyring-api@6.4.0 None 0 242 kB metamaskbot
npm/@metamask/providers@17.0.0 None 0 359 kB metamaskbot
npm/@metamask/snaps-sdk@4.4.1 network 0 718 kB metamaskbot
npm/bech32@2.0.0 None 0 10.2 kB junderw
npm/fast-xml-parser@4.4.0 None 0 169 kB amitgupta
npm/webextension-polyfill@0.12.0 None 0 205 kB addons-robot

🚮 Removed packages: npm/@metamask/json-rpc-engine@7.3.3, npm/@metamask/keyring-api@3.0.0, npm/@metamask/providers@14.0.2, npm/@metamask/snaps-sdk@1.4.0, npm/@noble/ed25519@1.7.3, npm/@noble/secp256k1@1.7.1, npm/fast-xml-parser@4.3.2, npm/is-svg@4.4.0, npm/json-rpc-middleware-stream@5.0.1, npm/webextension-polyfill@0.10.0

View full report↗︎

socket-security[bot] commented 1 month 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 Note
Network access npm/@metamask/snaps-sdk@4.4.1
Network access npm/@metamask/snaps-sdk@1.4.0

View full report↗︎

Next steps

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

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/snaps-sdk@4.4.1
  • @SocketSecurity ignore npm/@metamask/snaps-sdk@1.4.0
dependabot[bot] commented 1 month ago

Superseded by #394.