Skip to content
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

[Snyk] Upgrade gatsby-plugin-sharp from 5.0.0 to 5.13.1 #951

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

Conversation

X-oss-byte
Copy link
Owner

@X-oss-byte X-oss-byte commented Nov 22, 2024

snyk-top-banner

Snyk has created this PR to upgrade gatsby-plugin-sharp from 5.0.0 to 5.13.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 49 versions ahead of your current version.

  • The recommended version was released on 10 months ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Information Exposure
SNYK-JS-GATSBYPLUGINSHARP-5425803
429 No Known Exploit
medium severity Information Exposure
SNYK-JS-GATSBYPLUGINSHARP-5671648
429 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-SIDEWAYFORMULA-3317169
429 No Known Exploit
Release notes
Package name: gatsby-plugin-sharp
  • 5.13.1 - 2024-01-23
  • 5.13.0 - 2023-12-18
  • 5.13.0-next.1 - 2023-11-16
  • 5.13.0-next.0 - 2023-07-25
  • 5.13.0-alpha-alt-image-cdn.44 - 2023-11-03
  • 5.12.3 - 2023-10-26
  • 5.12.2 - 2023-10-20
  • 5.12.1 - 2023-10-09
  • 5.12.0 - 2023-08-24
  • 5.12.0-next.1 - 2023-07-03
  • 5.12.0-next.0 - 2023-06-15
  • 5.11.0 - 2023-06-15
  • 5.11.0-next.1 - 2023-06-05
  • 5.11.0-next.0 - 2023-05-16
  • 5.10.0 - 2023-05-16
  • 5.10.0-next.2 - 2023-05-03
  • 5.10.0-next.1 - 2023-04-27
  • 5.10.0-next.0 - 2023-04-18
  • 5.9.0 - 2023-04-18
  • 5.9.0-next.2 - 2023-04-06
  • 5.9.0-next.1 - 2023-03-30
  • 5.9.0-next.0 - 2023-03-21
  • 5.9.0-image-cdn-configurable.4 - 2023-04-11
  • 5.8.1 - 2023-03-29
  • 5.8.0 - 2023-03-21
  • 5.8.0-next.0 - 2023-02-16
  • 5.7.0 - 2023-02-21
  • 5.7.0-next.0 - 2023-02-03
  • 5.6.0 - 2023-02-07
  • 5.6.0-next.1 - 2023-01-26
  • 5.6.0-next.0 - 2023-01-19
  • 5.5.0 - 2023-01-24
  • 5.5.0-next.1 - 2023-01-17
  • 5.5.0-next.0 - 2023-01-05
  • 5.4.0 - 2023-01-10
  • 5.4.0-next.2 - 2023-01-04
  • 5.4.0-next.1 - 2022-12-14
  • 5.4.0-next.0 - 2022-12-08
  • 5.3.2 - 2022-12-14
  • 5.3.1 - 2022-12-14
  • 5.3.0 - 2022-12-13
  • 5.3.0-next.3 - 2022-12-07
  • 5.3.0-next.2 - 2022-12-06
  • 5.3.0-next.1 - 2022-12-01
  • 5.3.0-next.0 - 2022-11-25
  • 5.2.0 - 2022-11-25
  • 5.2.0-next.0 - 2022-11-17
  • 5.1.0 - 2022-11-22
  • 5.1.0-next.0 - 2022-11-08
  • 5.0.0 - 2022-11-08
from gatsby-plugin-sharp GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Summary by Sourcery

Bug Fixes:

  • Fix vulnerabilities related to information exposure and regular expression denial of service (ReDoS) by upgrading gatsby-plugin-sharp.

Snyk has created this PR to upgrade gatsby-plugin-sharp from 5.0.0 to 5.13.1.

See this package in npm:
gatsby-plugin-sharp

See this project in Snyk:
https://app.snyk.io/org/sammytezzy/project/20794044-5f49-41de-a492-223de49c2642?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

stackblitz bot commented Nov 22, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

sourcery-ai bot commented Nov 22, 2024

Reviewer's Guide by Sourcery

This PR upgrades gatsby-plugin-sharp from version 5.0.0 to 5.13.1 to address three medium severity security vulnerabilities. The upgrade is implemented through a direct version bump in the package.json file and its corresponding package-lock.json.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Dependency version upgrade to address security vulnerabilities
  • Updated gatsby-plugin-sharp version from ^5.0.0 to ^5.13.1
  • Fixed Information Exposure vulnerability (SNYK-JS-GATSBYPLUGINSHARP-5425803)
  • Fixed Information Exposure vulnerability (SNYK-JS-GATSBYPLUGINSHARP-5671648)
  • Fixed ReDoS vulnerability in sidewayformula dependency (SNYK-JS-SIDEWAYFORMULA-3317169)
starters/gatsby-starter-wordpress-blog/package.json
starters/gatsby-starter-wordpress-blog/package-lock.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.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a 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. You can also use
    this command to specify where the summary should be inserted.

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. It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!

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