revert 5f437970402866348dba9aab6a4c7e942d6c1d83

[jiexi]

Revert bad release merge

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​qrcode@​1.5.6 ⏵ 1.5.5				-7
	@​types/​react-dom@​19.2.2 ⏵ 19.2.1				+2
	expo-router@​6.0.13 ⏵ 6.0.12				+1
	expo@​54.0.20 ⏵ 54.0.13	+1		+1
	expo-system-ui@​6.0.8 ⏵ 6.0.7
	@​types/​node@​20.19.23 ⏵ 20.19.21
	react-native-web@​0.21.2 ⏵ 0.21.1				-2
	expo-image@​3.0.10 ⏵ 3.0.9	+1		+1	+1
	eslint@​9.38.0 ⏵ 9.37.0
	@​tailwindcss/​postcss@​4.1.16 ⏵ 4.1.14

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		@tailwindcss/oxide@4.1.14 has Network access. Module: https Location: Package overview From: ? → npm/@tailwindcss/postcss@4.1.14 → npm/@tailwindcss/oxide@4.1.14 ℹ 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/@tailwindcss/oxide@4.1.14. 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.
Block		@expo/metro@54.0.0 has a New author. New Author: bycedric Previous Author: philpl From: ? → npm/@expo/metro@54.0.0 ℹ Read more on: This package | This alert | What is new author? 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: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@expo/metro@54.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.
Warn		@tailwindcss/oxide@4.1.14 has Install scripts. Install script: postinstall Source: node ./scripts/install.js From: ? → npm/@tailwindcss/postcss@4.1.14 → npm/@tailwindcss/oxide@4.1.14 ℹ Read more on: This package | This alert | What is an install script? 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 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@tailwindcss/oxide@4.1.14. 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.
Warn		@emnapi/core@1.5.0 is a AI-detected potential code anomaly. Notes: This file implements a WASM/N-API runtime bridge (emnapi) exposing many napi_* functions, memory-view and buffer helpers, thread/worker management and threadsafe function queues. It uses dynamic function creation via new Function (with identifier validation), direct WebAssembly memory reads/writes (DataView/Uint8Array), Atomics/SharedArrayBuffer for cross-thread signaling, and postMessage transfers of ArrayBuffers. There is no evidence of malicious behavior (no network callbacks, no shell or file operations, no hard-coded secrets), but these powerful primitives can enable unexpected code execution or data movement if untrusted inputs reach them. Confidence: 1.00 Severity: 0.60 From: ? → npm/@tailwindcss/postcss@4.1.14 → npm/@emnapi/core@1.5.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/core@1.5.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.
Warn		@emnapi/runtime@1.5.0 is a AI-detected potential code anomaly. Notes: Overall, this code fragment is a standard and legitimate binding/runtime infrastructure for Node.js native addon interoperability (EMNAPI). There is no evidence of data exfiltration, remote control, backdoors, or malware behavior within this snippet. The primary security considerations relate to the complexity and correct handling of finalizers, weak references, and policy-driven warning paths; misconfiguration or misuse by host applications could introduce risk, but the code itself does not demonstrate malicious activity. Confidence: 1.00 Severity: 0.60 From: ? → npm/next@15.4.1 → npm/@tailwindcss/postcss@4.1.14 → npm/@emnapi/runtime@1.5.0 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@emnapi/runtime@1.5.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.
Warn		expo-router@6.0.12 is a AI-detected potential code anomaly. Notes: The code appears to be a conventional onboarding/tutorial component for Expo Router with environment-driven UI behavior and a user-initiated, likely safe, create-entry-file action. No malicious activity or data leakage is evident within this module. The primary security consideration is ensuring createEntryFileAsync operates within safe, restricted paths and does not overwrite critical files. Overall, the risk is low to moderate depending on the unseen implementation of createEntryFileAsync. Confidence: 1.00 Severity: 0.60 From: apps/rn-demo/package.json → npm/expo-router@6.0.12 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/expo-router@6.0.12. 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