chore: Bump @metamask/analytics-controller from 1.2.1 to 2.0.0

[dependabot]

Bumps @metamask/analytics-controller from 1.2.1 to 2.0.0.

Commits

• 492e4c3 Release/1163.0.0 (#9735)
• 687e0c9 fix(snap-account-service): move withSafeError catch in migration handler (#...
• 9bbce8d feat: persist pay strategy in TransactionController metamaskPay metadat...
• 0774efc feat(transaction-pay-controller): add generic non-atomic post-Relay flow via ...
• bb7a772 feat(core-backend): add debouncer system notifications in AccountActivity (#9...
• 63be32e fix(assets-controller): consume account activity (#9517)
• 7ef0821 fix(perps): prevent reduce-only close orders from increasing positions (#9719)
• 9a1b7e4 docs(analytics-controller): note geolocation resolves at most once per sessio...
• d5d1c63 feat(analytics-controller): resolve geolocation only after opt-in (#9728)
• e3f2004 Constrain MessengerAdapter to match given data services (#9475)
• Additional commits viewable in compare view

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​metamask/​analytics-controller@​1.2.1 ⏵ 2.0.0			+1

View full report

[socket-security]

Caution

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Network access: npm @metamask/geolocation-controller in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: ? → npm/@metamask/analytics-controller@2.0.0 → npm/@metamask/geolocation-controller@1.0.0 ℹ Read more on: This package | This alert | What is network access? Next steps: 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@socket.dev. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@metamask/geolocation-controller@1.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report