[Snyk] Security upgrade react-native from 0.73.1 to 0.73.5

[revan-zhang]

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• example/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Server-side Request Forgery (SSRF) SNYK-JS-IP-12704893	670
	Server-side Request Forgery (SSRF) SNYK-JS-IP-12761655	670

---

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:

🦉 Server-side Request Forgery (SSRF)

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-4d3efb8b50240a95254ec791d447b147

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[revan-zhang]

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

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	node-releases@​2.0.14
	side-channel@​1.0.4
	typed-array-buffer@​1.0.0
	which-collection@​1.0.1
	safer-buffer@​2.1.2
	typedarray@​0.0.6
	object.hasown@​1.1.3
	set-function-length@​1.1.1
	object.fromentries@​2.0.7
	path-parse@​1.0.7
	object-keys@​1.1.1
	safe-regex-test@​1.0.0
	unbox-primitive@​1.0.2
	safe-array-concat@​1.0.1
	typed-array-length@​1.0.4
	string.prototype.trim@​1.2.8
	object.entries@​1.1.7
	object.values@​1.1.7
	string.prototype.matchall@​4.0.10
	metro-cache-key@​0.80.12 ⏵ 0.80.2	+1		+1	+2
	typed-array-byte-length@​1.0.0
	typed-array-byte-offset@​1.0.0
	which-boxed-primitive@​1.0.2
	object.assign@​4.1.5
	safe-buffer@​5.2.1
	string.prototype.trimstart@​1.0.7
	string.prototype.trimend@​1.0.7
	reflect.getprototypeof@​1.0.4
	object-assign@​4.1.1
	nullthrows@​1.1.1
	metro-minify-terser@​0.80.12 ⏵ 0.80.2	+1		-1	+2
	tmpl@​1.0.5
	metro-babel-transformer@​0.80.12 ⏵ 0.80.2	+1		-2	+2
	unique-slug@​4.0.0
See 276 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		safer-buffer@2.1.2 has Obfuscated code. Confidence: 0.94 Location: Package overview From: yarn.lock → npm/safer-buffer@2.1.2 ℹ 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/safer-buffer@2.1.2. 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