[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):

• Example/package.json
• Example/yarn.lock

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.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	XML Injection SNYK-JS-XMLDOM-15869637	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 failed. 5 issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (5)
⛔	Open Source Security	0	3	2	0	5 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
	@​types/​react-native@​0.73.0
	lodash@​4.18.1
	@​types/​d3-shape@​3.1.0
	@​types/​d3-scale@​4.0.2
	react-native-gesture-handler@​2.30.0
	@​babel/​runtime@​7.18.6
	@​types/​react@​19.2.9
	@​babel/​core@​7.18.6
	react-native-redash@​16.3.0
	d3-shape@​3.1.0
	d3-scale@​4.0.2
	react-native-worklets@​0.7.2
	react@​19.2.3
	expo-haptics@​15.0.8
	react-native-svg@​15.15.1
	react-native@​0.63.2 ⏵ 0.69.12	+1	+16		+50
	typescript@​5.9.3
	react-native-reanimated@​4.2.1
	react-native@​0.63.2 ⏵ 0.83.1	+7	+16		+50

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		Obfuscated code: npm @react-native/debugger-frontend is 96.0% likely obfuscated Confidence: 0.96 Location: Package overview From: ? → npm/react-native@0.83.1 → npm/@react-native/debugger-frontend@0.83.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/@react-native/debugger-frontend@0.83.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.
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/react-native-svg@12.1.0 → npm/react-native-svg@15.15.1 → 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.

View full report

[devin-ai-integration]

Devin Review found 1 potential issue.

View 2 additional findings in Devin Review.

[devin-ai-integration]

🔴 react-native 0.69.12 requires React 18 but React is still pinned to 16.13.1

react-native was bumped from 0.63.2 to 0.69.12, but react remains pinned at 16.13.1 (line 17) and react-test-renderer at 16.13.1 (line 36). React Native 0.69.12 has a peer dependency on react: 18.0.0. This version mismatch will cause peer dependency warnings and likely runtime failures, as React Native 0.69 relies on React 18 internals.

Prompt for agents

In Example/package.json, react-native was upgraded to 0.69.12 which requires react 18.0.0 as a peer dependency. The react version on line 17 needs to be updated from 16.13.1 to 18.0.0, and react-test-renderer on line 36 should also be updated to match (18.0.0). Other dependencies like react-native-reanimated (currently ^2.0.0-alpha.7) may also need version bumps to be compatible with React Native 0.69.

---

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