Skip to content

Conversation

@Dargon789
Copy link
Owner

@Dargon789 Dargon789 commented Mar 12, 2025

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/app/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 Regular Expression Denial of Service (ReDoS)
SNYK-JS-BABELHELPERS-9397697
  141  
medium severity Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
  131  

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)

Summary by Sourcery

Updates yarn dependencies to fix two vulnerabilities: a Regular Expression Denial of Service (ReDoS) vulnerability and a Missing Release of Resource after Effective Lifetime vulnerability.

Bug Fixes:

  • Fixes a Regular Expression Denial of Service (ReDoS) vulnerability by updating the @svgr/core dependency.
  • Fixes a Missing Release of Resource after Effective Lifetime vulnerability by updating the shelljs dependency.

@sourcery-ai
Copy link

sourcery-ai bot commented Mar 12, 2025

Reviewer's Guide by Sourcery

This pull request updates two dependencies, @svgr/core and shelljs, in packages/app/package.json to address identified vulnerabilities. @svgr/core was updated from version 5.5.0 to 7.0.0 to resolve a Regular Expression Denial of Service (ReDoS) vulnerability. shelljs was updated from version 0.8.5 to 0.9.0 to resolve a missing release of resource after effective lifetime vulnerability.

Updated class diagram for package.json dependencies

classDiagram
  class package_json {
    -dependencies
    -devDependencies
  }

  note for package_json "@svgr/core updated from 5.5.0 to 7.0.0\nshelljs updated from 0.8.5 to 0.9.0"
Loading

File-Level Changes

Change Details Files
Updated @svgr/core dependency to address a Regular Expression Denial of Service (ReDoS) vulnerability.
  • Upgraded @svgr/core from version 5.5.0 to 7.0.0.
packages/app/package.json
Updated shelljs dependency to address a missing release of resource after effective lifetime vulnerability.
  • Upgraded shelljs from version 0.8.5 to 0.9.0.
packages/app/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

@snyk-io
Copy link

snyk-io bot commented Mar 12, 2025

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

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

@Dargon789 Dargon789 merged commit a9917f5 into main Mar 13, 2025
16 of 20 checks passed
@Dargon789 Dargon789 deleted the snyk-fix-a4b2b4b4c97c97afab686cdd390d8bfd branch March 13, 2025 05:01
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.

3 participants