Skip to content

[Snyk] Security upgrade expo from 52.0.9 to 53.0.0#69

Open
Dargon789 wants to merge 1 commit into
mainfrom
snyk-fix-ab5856636c0858bae40410e214c9d05f
Open

[Snyk] Security upgrade expo from 52.0.9 to 53.0.0#69
Dargon789 wants to merge 1 commit into
mainfrom
snyk-fix-ab5856636c0858bae40410e214c9d05f

Conversation

@Dargon789

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • apps/mobile/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
medium severity Improper Handling of Unicode Encoding
SNYK-JS-TAR-15038581
  713  

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.

@vercel

vercel Bot commented Jan 22, 2026

Copy link
Copy Markdown
Contributor

Deployment failed with the following error:

Resource is limited - try again in 11 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/dargon789-forge?upgradeToPro=build-rate-limit

@snyk-io

snyk-io Bot commented Jan 22, 2026

Copy link
Copy Markdown

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

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a security vulnerability by performing a major version upgrade of the expo framework. The primary goal is to enhance the project's security posture by updating a critical dependency, though it necessitates manual intervention for the lock file and careful review for compatibility due to the significant version jump.

Highlights

  • Security Upgrade: This pull request, automatically generated by Snyk, aims to fix one medium-severity vulnerability (SNYK-JS-TAR-15038581: Improper Handling of Unicode Encoding) by upgrading the expo dependency.
  • Dependency Update: The expo package in apps/mobile/package.json has been upgraded from version 52.0.9 to 53.0.0.
  • Manual Intervention Required: The yarn.lock file was not updated by Snyk, requiring manual update before merging. Additionally, users of Yarn's zero-installs feature will need to run yarn to update the .yarn/cache/ directory.
  • Potential Breaking Changes: As this is a major version upgrade for expo, it's important to check the changes to ensure they don't introduce breaking issues with the project.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the expo dependency to address a security vulnerability. While the package.json has been updated, the yarn.lock file was not updated, which is crucial for ensuring the new dependency version is actually used and for maintaining consistent dependency resolution across environments. Please ensure yarn.lock is updated and committed.

Comment thread apps/mobile/package.json
"dayjs": "1.11.7",
"ethers": "6.0.0",
"expo": "52.0.9",
"expo": "53.0.0",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

The package.json has been updated to expo@53.0.0, which is good for addressing the reported vulnerability. However, the pull request description indicates that yarn.lock failed to update. It is critical to ensure yarn.lock is properly updated to reflect this change. Without an updated yarn.lock, the new version of expo might not be installed consistently, potentially leaving the vulnerability unaddressed in some environments or causing dependency conflicts. Please run yarn install or yarn to update yarn.lock and commit the changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants