[Snyk] Security upgrade gatsby from 2.32.13 to 5.14.0

[saurabharch]

Snyk has created this PR to fix 3 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• examples/using-hjson/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Server-side Request Forgery (SSRF) SNYK-JS-IP-12704893	788
	Server-side Request Forgery (SSRF) SNYK-JS-IP-12761655	788
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-12613773	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:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Server-side Request Forgery (SSRF)

[gemini-code-assist]

Summary of Changes

Hello @saurabharch, I'm Gemini Code Assist¹! 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, automatically generated by Snyk, aims to enhance the project's security posture by upgrading the gatsby dependency. This critical update resolves three identified vulnerabilities, including high-severity Server-side Request Forgery issues and a resource allocation vulnerability, ensuring a more secure and stable application environment.

Highlights

• Automated Security Upgrade: This pull request was automatically generated by Snyk to address identified security vulnerabilities.
• Vulnerability Resolution: Three vulnerabilities have been fixed, including two high-severity Server-side Request Forgery (SSRF) issues and one medium-severity Allocation of Resources Without Limits or Throttling vulnerability.
• Dependency Upgrade: The gatsby dependency has been upgraded from version 2.32.13 to 5.14.0 to resolve these security concerns.

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

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]

Code Review

This pull request, automatically generated by Snyk, upgrades gatsby from version 2 to 5 to address security vulnerabilities. While this is a necessary security update, it's a major version jump that introduces significant breaking changes. The current change only updates the gatsby package itself, leaving other critical dependencies like react, react-dom, and various Gatsby plugins at incompatible versions. This will cause the application build to fail. A more comprehensive update of related dependencies is required for this upgrade to be successful.

[gemini-code-assist]

Upgrading gatsby from v2 to v5 is a major change with several breaking dependency requirements that are not addressed in this automated PR. To ensure the project builds and runs correctly, other dependencies must also be updated.

1. React Version: Gatsby v5 requires React 18. The current react and react-dom versions (^16.3.2) are incompatible and must be upgraded.
2. Gatsby Plugins: Gatsby plugins should be aligned with the core gatsby version. gatsby-source-filesystem and gatsby-transformer-hjson need to be upgraded to their v5 counterparts.
3. Core-js: Starting with Gatsby v3, it is recommended to use core-js@3.

Here is a suggested dependencies block with the necessary updates:

  "dependencies": {
    "core-js": "^3.0.0",
    "gatsby": "^5.14.0",
    "gatsby-source-filesystem": "^5.14.0",
    "gatsby-transformer-hjson": "^5.14.0",
    "react": "^18.2.0",
    "react-dom": "^18.2.0"
  }

Without these additional changes, the application will fail to build. It is also advisable to consult the official Gatsby migration guides (v2 to v3, v3 to v4, and v4 to v5) for any code-level API changes and to test thoroughly.