Skip to content

[Snyk] Security upgrade gatsby-cli from 5.10.0 to 5.14.0 #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

St0nersdash
Copy link
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):

  • package.json
  • 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
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-BABELRUNTIME-10044504
  738  

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:

🦉 Regular Expression Denial of Service (ReDoS)

Copy link

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

Choose a reason for hiding this comment

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

Hello @St0nersdash, 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!

Summary of Changes

This pull request, created by Snyk, upgrades the gatsby-cli dependency from version 5.10.0 to 5.14.0. The primary intent is to address a Regular Expression Denial of Service (ReDoS) vulnerability, identified as SNYK-JS-BABELRUNTIME-10044504, which has a medium severity score of 738. The changes involve modifications to package.json to update the gatsby-cli version and corresponding updates to yarn.lock to reflect the new dependency versions and their transitive dependencies.

Highlights

  • Security Upgrade: Addresses a medium severity Regular Expression Denial of Service (ReDoS) vulnerability (SNYK-JS-BABELRUNTIME-10044504) in gatsby-cli.
  • Dependency Update: Upgrades gatsby-cli from version 5.10.0 to 5.14.0 in package.json.
  • Yarn Lockfile Update: Updates yarn.lock to reflect the changes in dependencies due to the gatsby-cli upgrade, including removing older versions of transitive dependencies.

Changelog

Click here to see the changelog
  • package.json
    • Upgraded gatsby-cli dependency from version 5.10.0 to 5.14.0 to address a security vulnerability.
  • yarn.lock
    • Removed older versions of dependencies related to gatsby-cli.
    • Updated dependency versions to align with the new gatsby-cli version 5.14.0.
    • Removed @turist/fetch@^7.2.0 and @turist/time@^0.0.2.
    • Removed @types/node-fetch@2.
    • Removed arch@^2.1.1.
    • Removed clipboardy@^2.3.0.
    • Removed create-gatsby@^3.10.0.
    • Consolidated cross-spawn version to cross-spawn@^6.0.5.
    • Removed envinfo@^7.8.1.
    • Removed execa@^1.0.0.
    • Removed form-data@^3.0.0.
    • Removed gatsby-cli@^5.10.0.
    • Removed gatsby-telemetry@^4.10.0.
    • Removed get-stream@^4.0.0.
    • Removed git-up@^7.0.0.
    • Consolidated is-docker version to is-docker@^2.0.0, is-docker@^2.1.1.
    • Removed is-ssh@^1.4.0 and is-stream@^1.1.0.
    • Removed node-fetch@^2.6.9.
    • Removed npm-run-path@^2.0.0.
    • Removed p-finally@^1.0.0.
    • Removed parse-path@^7.0.0 and parse-url@^8.1.0.
    • Consolidated path-key version to path-key@^2.0.1.
    • Removed protocols@^2.0.0, protocols@^2.0.1.
    • Consolidated signal-exit version to signal-exit@^3.0.2, signal-exit@^3.0.3, signal-exit@^3.0.7.
    • Removed strip-eof@^1.0.0.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.


A ReDoS threat,
Gatsby's CLI gets an update,
Safe code we create.

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.

Copy link

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

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 addresses a medium severity security vulnerability by upgrading the gatsby-cli dependency. The changes primarily involve updating package.json and yarn.lock. It's important to ensure that this upgrade doesn't introduce any breaking changes or regressions in the project's functionality.

Summary of Findings

  • Security Vulnerability Fix: This PR upgrades the gatsby-cli dependency to address a Regular Expression Denial of Service (ReDoS) vulnerability. It's crucial to verify the upgrade doesn't introduce any regressions.
  • Yarn Lockfile Changes: The PR includes significant changes to yarn.lock. Review these changes to ensure no unintended dependencies were added or removed.

Merge Readiness

The pull request addresses a security vulnerability, which is a positive step. However, due to the nature of dependency upgrades and the potential for regressions, I recommend careful testing and verification of the application's functionality after this change. Given the medium severity of the vulnerability, I recommend addressing it promptly, but not before thoroughly testing the changes. I am unable to approve this pull request, and other reviewers should carefully examine the changes and approve before merging.

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