chore(dependencies): @metamask/eth-token-tracker@^7.0.2->^8.0.0

[legobeat]

Description

• Update @metamask/eth-token-tracker from ^7.0.2 to ^8.0.0.

  • https://github.com/MetaMask/eth-token-tracker/blob/main/CHANGELOG.md
  • https://github.com/MetaMask/eth-block-tracker/blob/main/CHANGELOG.md

• Update @metamask/eth-json-rpc-middleware from ^12.1.0 to ^12.1.1.

  • https://github.com/MetaMask/eth-json-rpc-middleware/blob/main/CHANGELOG.md

Related issues

• Prevent multiple simultaneous polling loops eth-block-tracker#208
• fix: @metamask/transaction-controller@^29.1.0->^30.0.0 #24861
• deps: @metamask/transaction-controller@^29.1.0->^30.0.0 smart-transactions-controller#342

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask 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.

[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]	None	0	0 B
npm/@metamask/[email protected]	None	0	5.55 MB	metamaskbot
npm/@metamask/[email protected]	Transitive: network	+1	833 kB	metamaskbot
npm/@metamask/[email protected]	network	0	673 kB	metamaskbot
npm/@sentry/[email protected]	environment, filesystem, network, shell	0	55.8 kB	sentry-bot

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

View full report↗︎

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.77%. Comparing base (0df1d57) to head (7415c93).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #24855      +/-   ##
===========================================
- Coverage    65.77%   65.77%   -0.00%     
===========================================
  Files         1366     1366              
  Lines        54254    54254              
  Branches     14101    14101              
===========================================
- Hits         35685    35684       -1     
- Misses       18569    18570       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[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
Install scripts	npm/@sentry/[email protected]	Install script: install Source: node ./scripts/install.js	package.json
Network access	npm/@sentry/[email protected]	Module: http Location: Package overview	package.json

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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

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

[legobeat]

The @socket-security alert about npm/@sentry/[email protected] is unrelated to anything in this PR. I am not sure why it's coming up here. @naugtur