Merge individual branch fixes into devin/fix-issues/505257/merge

[devin-ai-integration]

Merge individual branch fixes into devin/fix-issues/505257/merge

This pull request merges the changes from the following branches into the devin/fix-issues/505257/merge branch, as part of the task to consolidate fixes for the metamask-mobile repository:

• devin/fix-issues/505257/4
• devin/fix-issues/505257/6
• devin/fix-issues/505257/5
• devin/fix-issues/505257/8
• devin/fix-issues/505257/3

All branches have been successfully merged, and subsequent tests and linting checks have been performed to ensure code quality and functionality.

Link to Devin run: https://preview.devin.ai/devin/2436f990397344b797a3e5f73ef2992b

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/[email protected]	environment	+1	9.91 MB	metamaskbot
npm/[email protected]	None	0	52.6 kB	marijn
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+47	5.93 MB	simenb

🚮 Removed packages: npm/@metamask/[email protected]

View full report↗︎

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

Alert	Package	Note	Source	CI
Deprecated	npm/[email protected]	Reason: Use your platform's native atob() and btoa() methods instead	package.json	🚫
New author	npm/[email protected]	New Author: domenic Previous Author: timothygu	package.json	🚫
Deprecated	npm/[email protected]	Reason: Use your platform's native DOMException instead	package.json	🚫
Network access	npm/[email protected]	Module: https-proxy-agent Location: Package overview	package.json	🚫
Network access	npm/[email protected]	Module: http Location: Package overview	package.json	🚫
Network access	npm/[email protected]	Module: http-proxy-agent Location: Package overview	package.json	🚫
Network access	npm/[email protected]	Module: https Location: Package overview	package.json	🚫
Shell access	npm/[email protected]	Module: child_process Location: Package overview	package.json	🚫

View full report↗︎

Next steps

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

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.

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.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]