chore: upgrade signature controller to remove global network

[matthewwalsh0]

Description

Upgrade @metamask/signature-controller to remove the global network usage.

Related issues

Manual testing steps

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask-previews/signature-controller@20.1.0-preview-1800a170	Transitive: environment, network	+9	2.11 MB	metamaskbot

🚮 Removed packages: npm/@metamask/signature-controller@20.0.0

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
Network access	npm/@metamask/eth-json-rpc-middleware@15.0.0	Module: globalThis["fetch"] Location: Package overview	package.json	🚫
New author	npm/@metamask/eth-json-rpc-infura@10.0.0	New Author: lgbot Previous Author: mcmire	package.json	🚫
Unstable ownership	npm/@metamask/eth-json-rpc-infura@10.0.0	Author: lgbot	package.json	🚫
Network access	npm/@metamask/eth-json-rpc-infura@10.0.0	Module: globalThis["fetch"] Location: Package overview	package.json	🚫

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.

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 unstable ownership?

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

Try to reduce the amount of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

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/eth-json-rpc-middleware@15.0.0
• @SocketSecurity ignore npm/@metamask/eth-json-rpc-infura@10.0.0

[metamaskbot]

Builds ready [fc9b79f]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6
  • common: 0, 1, 10, 11, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • offscreen: 0
  • ui: 0, 1, 10, 11, 12, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1768 ± 39 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	1595	1934	1777	83	40
		domContentLoaded	1582	1869	1740	67	32
		load	1592	1929	1768	82	39
		domInteractive	20	72	41	13	6
		backgroundConnect	9	74	25	17	8
		firstReactRender	44	188	86	33	16
		getState	5	67	15	19	9
		initialActions	0	0	0	0	0
		loadScripts	1145	1394	1288	64	31
		setupStore	11	66	32	23	11
		uiStartup	1782	2244	1965	105	50

Bundle size diffs [🚨 Warning! Bundle size has increased!]

• background: 18.37 KiB (0.42%)
• ui: -20 Bytes (-0.00%)
• common: 0 Bytes (0.00%)