deps: @metamask/utils@^4.0.0->^5.0.1

[legobeat]

• 5.0.1: Keep original type when using hasProperty if defined (Keep original type when using hasProperty if defined utils#94)
• 5.0.0: BREAKING: Update Keyring type (Update Keyring type utils#89)
  • The Keyring class now uses the data types TypedTransaction and TxData from @ethereumjs/tx (v4.1.1).
  • The Keyring now exposes a new optional method called generateRandomMnemonic.

• CHANGELOG
• MetaMask/utils@v4.0.0...MetaMask:utils:v5.0.1

This was carefully crafted to avoid triggering dependency bumps breaking Node.js v14 support. This will likely be the last dependency bump before removing Node.js v14 support for this package.

Blocking

• 8.1.2 #89
  • Remove support for Node.js 14 #91
    • deps: Update eth-json-rpc and metamask packages #95

[socket-security]

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

Packages	Version	New capabilities	Transitives	Size	Publisher
@metamask/utils	4.0.0...5.0.1	network	+46/-0	6.43 MB	metamaskbot

[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: bech32@1.1.4, @chainsafe/as-sha256@0.3.1, @ethersproject/properties@5.7.0, @ethersproject/random@5.7.0, @ethersproject/abstract-signer@5.7.0, brorand@1.1.0, @ethersproject/basex@5.7.0, @ethersproject/constants@5.7.0, @ethersproject/signing-key@5.7.0, minimalistic-assert@1.0.1, @ethersproject/logger@5.7.0, @ethersproject/sha2@5.7.0, crc-32@1.2.2, bn.js@4.12.0, bn.js@5.2.1, case@1.6.3, @ethersproject/hash@5.7.0, @ethersproject/strings@5.7.0, @ethersproject/rlp@5.7.0, @ethersproject/abstract-provider@5.7.0, hash.js@1.1.7, elliptic@6.5.4, @ethersproject/address@5.7.0, @ethersproject/keccak256@5.7.0, minimalistic-crypto-utils@1.0.1, @ethersproject/transactions@5.7.0, @ethersproject/bignumber@5.7.0, @ethersproject/base64@5.7.0, @ethersproject/bytes@5.7.0, hmac-drbg@1.0.1, @ethersproject/web@5.7.1

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