[Snyk] Security upgrade react-native from 0.77.0 to 0.85.0

[revan-zhang]

Snyk has created this PR to fix 1 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
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	535

---

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.

---

[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]

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.77.0 → npm/@react-native/debugger-frontend@0.77.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/@react-native/debugger-frontend@0.77.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]

🔴 Incomplete react-native upgrade: @react-native/ companion packages left at 0.77.0*

The PR bumps react-native from 0.77.0 to 0.85.0, but the @react-native/babel-preset, @react-native/metro-config, and @react-native/typescript-config devDependencies at example/package.json:23-25 are all still pinned to 0.77.0. These packages are versioned in lockstep with react-native (they were all previously aligned at 0.77.0), so this version mismatch will likely cause build failures or runtime errors. Additionally, the @react-native-community/cli packages at example/package.json:20-22 were also matched to the 0.77.0 release and may need updating as well.

Prompt for agents

The react-native dependency was bumped from 0.77.0 to 0.85.0, but the companion @react-native/* packages in devDependencies (lines 23-25: @react-native/babel-preset, @react-native/metro-config, @react-native/typescript-config) are still at 0.77.0. These must be updated to match the react-native version (0.85.0 or whatever version aligns with RN 0.85). The @react-native-community/cli packages (lines 20-22) may also need updating. The react version (line 13, currently 18.3.1) should also be checked for compatibility with RN 0.85. Additionally, the root package.json still lists react-native 0.77.0 as a devDependency (line 82), which may also need updating for consistency.

---

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