[Snyk] Security upgrade react-native from 0.74.1 to 0.76.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
	XML Entity Expansion SNYK-JS-FASTXMLPARSER-15677840	710

---

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
Upgrading react-native across minor versions can introduce breaking runtime/build changes in the example app and its native tooling, despite being a targeted dependency bump.

Overview
Updates the example app dependency on react-native from 0.74.1 to 0.76.0 in example/package.json to address a reported vulnerability (via transitive deps).

^{Written by Cursor Bugbot for commit 76f091f. 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
	eslint@​8.57.1
	jest@​29.7.0
	react-test-renderer@​18.2.0
	jpush-react-native@​3.2.6
	typescript@​5.0.4
	prettier@​2.8.8
	react-native@​1000.0.0 ⏵ 0.76.0	+10			+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 flow-parser is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@react-native/babel-preset@0.74.83 → npm/react-native@0.76.0 → npm/flow-parser@0.305.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/flow-parser@0.305.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

[devin-ai-integration]

Devin Review found 1 potential issue.

View 1 additional finding in Devin Review.

[devin-ai-integration]

🟡 devDependencies @react-native/* packages not updated to match new react-native 0.76.0

react-native is bumped from 0.74.1 to 0.76.0, but the @react-native/babel-preset, @react-native/eslint-config, @react-native/metro-config, and @react-native/typescript-config devDependencies remain pinned at 0.74.83. These @react-native/* packages are part of the react-native monorepo and are versioned in lockstep with it. Using 0.74.83 tooling with react-native 0.76.0 will likely cause Metro bundler configuration incompatibilities or build failures in the example app, as each major react-native release expects the matching versions of these companion packages.

Prompt for agents

In example/package.json, update the @react-native/* devDependencies on lines 22-25 to versions matching react-native 0.76.0. These packages are released in lockstep with react-native from the same monorepo. The correct versions would be the 0.76.x variants, e.g.:

  "@react-native/babel-preset": "0.76.0",
  "@react-native/eslint-config": "0.76.0",
  "@react-native/metro-config": "0.76.0",
  "@react-native/typescript-config": "0.76.0"

Also verify that react 18.2.0 is compatible with react-native 0.76.0 (react-native 0.76 typically expects react 18.3.1).

---

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

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

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

[cursor]

Mismatched React version for React Native 0.76.0

High Severity

react-native was bumped to 0.76.0 but react remains at 18.2.0. React Native 0.76.0 expects react 18.3.1 as its peer dependency. This version mismatch will cause npm peer dependency errors during install and may lead to runtime incompatibilities, since 0.76.0 depends on APIs and deprecation warnings introduced in React 18.3.

 

[cursor]

Dev dependencies not updated for React Native 0.76

High Severity

react-native was bumped to 0.76.0 but @react-native/babel-preset, @react-native/eslint-config, @react-native/metro-config, and @react-native/typescript-config all remain pinned at 0.74.83. These packages are versioned in lockstep with react-native and need to be 0.76.x. Notably, the babel preset 0.76 enables the Hermes parser by default, which is required for correct transpilation in 0.76.