[Snyk] Fix for 3 vulnerabilities

[revan-zhang]

Snyk has created this PR to fix 3 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
	XML Injection SNYK-JS-XMLDOMXMLDOM-15869636	660
	Arbitrary Code Injection SNYK-JS-LODASH-15869625	630
	Prototype Pollution SNYK-JS-LODASH-15869619	545

---

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:

🦉 Prototype Pollution
🦉 Arbitrary Code Injection
🦉 XML Injection

---

[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
	eslint@​8.57.1
	text-encoding@​0.7.0
	rimraf@​2.7.1 ⏵ 3.0.2	+1		+1
	https-browserify@​1.0.0
	@​typescript-eslint/​parser@​6.21.0
	@​types/​web-bluetooth@​0.0.17
	@​types/​w3c-web-usb@​1.0.10
	lodash@​4.17.21
	string_decoder@​1.3.0
	bytebuffer@​5.0.1
	events@​3.3.0
	process@​0.11.10
	stream-browserify@​3.0.0
	buffer@​6.0.3
	browserify-zlib@​0.2.0
	path-browserify@​1.0.1
	axios@​1.12.2
	@​typescript-eslint/​eslint-plugin@​6.21.0
	jszip@​3.10.1
	long@​4.0.0
	punycode@​2.3.1
	eslint-plugin-react@​7.37.5
	url@​0.11.4
	eslint-plugin-import@​2.32.0
	@​noble/​hashes@​1.3.3 ⏵ 1.8.0
	crypto-browserify@​3.12.1
	util@​0.12.5
	react-native-ble-plx@​3.5.1
	typescript@​5.3.3

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: 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/elliptic@6.5.5 ℹ 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.5. 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		Protestware or unwanted behavior: npm es5-ext Note: The script attempts to run a local post-install script, which could potentially contain malicious code. The error handling suggests that it is designed to fail silently, which is a common tactic in malicious scripts. From: ? → npm/es5-ext@0.10.64 ℹ Read more on: This package | This alert | What is protestware? 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: Consider that consuming this package may come along with functionality unrelated to its primary purpose. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es5-ext@0.10.64. 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

[devin-ai-integration]

Devin Review found 1 potential issue.

View 2 additional findings in Devin Review.

[devin-ai-integration]

🔴 Expo 53 upgrade breaks web build due to incompatible @expo/webpack-config dependency

Bumping expo from ^50.0.20 to ^53.0.0 creates a peer dependency conflict with @expo/webpack-config@^19.0.1 (line 16), whose latest version (19.0.1) declares peerDependencies: { "expo": "^49.0.7 || ^50.0.0-0" }. No newer version of @expo/webpack-config exists that supports Expo 53 — Expo deprecated webpack for web after SDK 50. Additionally, app.json:32 configures "bundler": "webpack", which is no longer supported in Expo 53. The web, dev:electron-web, and build:electron-web scripts will all fail.

Prompt for agents

The expo version was bumped from ^50 to ^53, but this is incompatible with the rest of the project setup:

1. @expo/webpack-config@^19.0.1 (package.json line 16) only supports expo ^49 or ^50. No newer version supports expo 53. Expo dropped webpack support after SDK 50.
2. app.json (line 32) sets web bundler to webpack, which is not supported in Expo 53.
3. Several other expo-* sub-packages are still at Expo 50-era versions (expo-clipboard ~5.0.0, expo-document-picker ~11.10.1, expo-image-manipulator ~11.8.0, expo-image-picker ~14.7.1, expo-localization ~14.8.4, expo-status-bar ~1.11.1) and may have runtime incompatibilities with Expo 53.
4. react-native 0.73.7 and react 18.2.0 are from the Expo 50 era.

If this PR is just to fix vulnerabilities, consider either:
- Reverting the expo bump and only keeping the lodash and other safe updates
- Doing a complete Expo SDK 53 migration including updating react, react-native, all expo-* packages, migrating from webpack to Metro for web, and removing @expo/webpack-config

---

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