Bump @metamask/utils to 6.0.1

[Mrtenz]

This bumps @metamask/utils to the latest version, 6.0.1.

[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
Network access	micro-ftch	0.3.1	Module: globalThis["fetch"] Location: index.js	package.json via @metamask/utils@6.0.1
No bug tracker	micro-ftch	0.3.1	Location: package.json	package.json via @metamask/utils@6.0.1
Unmaintained	micro-ftch	0.3.1	Last Publish: 7/8/2021, 4:10:57 AM	package.json via @metamask/utils@6.0.1
No contributors or author data	@ethereumjs/common	3.1.2	Location: package.json	package.json via @metamask/utils@6.0.1
No bug tracker	@chainsafe/ssz	0.11.1	Location: package.json	package.json via @metamask/utils@6.0.1
Unmaintained	crc-32	1.2.2	Last Publish: 4/4/2022, 11:05:52 PM	package.json via @metamask/utils@6.0.1

Next steps

What is network access?

This module accesses the network.

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

Why are bug trackers important?

Package does not have a linked bug tracker in package.json.

Add a bugs field to package.json. https://docs.npmjs.com/cli/v8/configuring-npm/package-json#bugs

What are unmaintained packages?

Package has not been updated in more than a year and may be unmaintained. Problems with the package may go unaddressed.

Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Why is contributor and author data important?

Package does not specify a list of contributors or an author in package.json.

Add a author field or contributors array to package.json.

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 @ethereumjs/common@3.1.2
• @SocketSecurity ignore @chainsafe/ssz@0.11.1
• @SocketSecurity ignore micro-ftch@0.3.1
• @SocketSecurity ignore crc-32@1.2.2

[socket-security]

New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎

Packages		Version	New capabilities	Transitives1	Size	Publisher
@metamask/utils	⬆️	3.6.0...6.0.1	network	+14/-0	4.78 MB	metamaskbot

Footnotes

1. https://docs.socket.dev ↩