[Snyk] Security upgrade react-native from 0.73.7 to 0.74.0

[revan-zhang]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• packages/connect-examples/expo-example/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Validation of Specified Quantity in Input SNYK-JS-FASTXMLPARSER-15699647	685

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

---

Note

Medium Risk
Dependency upgrade in a React Native/Expo app can introduce runtime or native build regressions, but the diff is limited to a single version bump in package.json.

Overview
Updates the expo-example app dependency on react-native from 0.73.7 to 0.74.0 to address a reported vulnerability via a security upgrade.

^{Written by Cursor Bugbot for commit 61a9708. This will update automatically on new commits. Configure here.}

---

[revan-zhang]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@​16.0.10
	node-fetch@​2.7.0
	nextra@​4.6.0
	lodash@​4.17.21
	buffer@​6.0.3
	events@​3.3.0
	process@​0.11.10
	nextra-theme-docs@​4.6.0
	@​onekeyfe/​hd-common-connect-sdk@​1.1.15
	@​types/​react@​19.2.7
	lottie-react@​2.4.1
	@​reactour/​tour@​3.8.0
	@​types/​node@​16.18.105 ⏵ 24.10.1			+1	-1
	cross-env@​7.0.3
	ripple-keypairs@​1.3.0
	postcss@​8.5.6
	gsap@​3.14.2
	debug@​4.4.1 ⏵ 4.3.4
	tailwindcss@​4.1.17
	react@​19.2.0
	cheerio@​1.0.0-rc.12
	@​xstate/​react@​6.0.0
	@​noble/​hashes@​1.4.0 ⏵ 1.3.1
	pagefind@​1.4.0
	assert@​2.0.0
	prismjs@​1.30.0
	electron@​28.2.3
	autoprefixer@​10.4.22
	xstate@​5.25.0
	typescript@​5.9.3
	parcel@​2.9.3
	react-syntax-highlighter@​16.1.0
	react-dom@​19.2.0
See 3 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: npm cipher-base is missing type checks, leading to hash rewind and passing on crafted data CVE: GHSA-cpq7-6gpm-g9rc cipher-base is missing type checks, leading to hash rewind and passing on crafted data (CRITICAL) Affected versions: < 1.0.5 Patched version: 1.0.5 From: ? → npm/ripple-keypairs@1.3.0 → npm/cipher-base@1.0.4 ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/cipher-base@1.0.4. 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		Critical CVE: Elliptic's private key extraction in ECDSA upon signing a malformed input (e.g. a string) CVE: GHSA-vjh7-7g9h-fjfh Elliptic's private key extraction in ECDSA upon signing a malformed input (e.g. a string) (CRITICAL) Affected versions: < 6.6.1 Patched version: 6.6.1 From: ? → npm/ripple-keypairs@1.3.0 → npm/elliptic@6.5.4 ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/elliptic@6.5.4. 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		Critical CVE: npm sha.js is missing type checks leading to hash rewind and passing on crafted data CVE: GHSA-95m3-7q98-8xr5 sha.js is missing type checks leading to hash rewind and passing on crafted data (CRITICAL) Affected versions: < 2.4.12 Patched version: 2.4.12 From: ? → npm/ripple-keypairs@1.3.0 → npm/sha.js@2.4.11 ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/sha.js@2.4.11. 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		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/cheerio@1.0.0-rc.12 → npm/entities@4.5.0 ℹ Read more on: This package | This alert | What is obfuscated code? 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 obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.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		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/nextra@4.6.0 → npm/entities@6.0.1 ℹ Read more on: This package | This alert | What is obfuscated code? 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 obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@6.0.1. 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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

React Native 0.74 incompatible with Expo SDK 50

High Severity

Upgrading react-native to 0.74.0 while expo remains at ^50.0.20 will break the build. Expo SDK 50 only supports React Native 0.73.x; React Native 0.74 requires Expo SDK 51. Additionally, react-native-reanimated at ~3.6.2 does not support React Native 0.74 — its compatibility range tops out at 0.73. These version mismatches will cause build or runtime failures.

Additional Locations (1)

• packages/connect-examples/expo-example/package.json#L49-L50

 

[devin-ai-integration]

Devin Review found 1 potential issue.

View 3 additional findings in Devin Review.

[devin-ai-integration]

🟡 @types/react-native not updated to match new react-native version

The PR bumps react-native from 0.73.7 to 0.74.0 (line 68) but does not update @types/react-native which remains at ~0.73.0 (line 95). This version mismatch means the type definitions will correspond to the 0.73.x API surface rather than 0.74.x, potentially causing incorrect type checking — either missing new APIs or referencing removed/changed ones.

Prompt for agents

In packages/connect-examples/expo-example/package.json, update the @types/react-native version in devDependencies (line 95) from ~0.73.0 to ~0.74.0 to match the react-native runtime version being bumped to 0.74.0 on line 68. Note: React Native 0.74 may ship its own types, in which case the @types/react-native dependency may no longer be needed at all — check whether the built-in types from react-native 0.74.0 are sufficient and remove the @types/react-native devDependency if so.

---

Was this helpful? React with 👍 or 👎 to provide feedback.