[Snyk] Fix for 3 vulnerabilities

[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-medium/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 bolster the project's security posture by resolving three critical vulnerabilities found within its npm dependencies. By upgrading key packages like gatsby and gatsby-source-medium, the PR mitigates risks associated with Server-side Request Forgery and resource allocation issues, ensuring a more secure and stable application environment.

Highlights

• Automated Security Fix: This pull request was automatically generated by Snyk to address three identified vulnerabilities in the project's npm dependencies.
• Vulnerabilities Addressed: Two high-severity Server-side Request Forgery (SSRF) vulnerabilities and one medium-severity Allocation of Resources Without Limits or Throttling vulnerability are being fixed.
• Dependency Upgrades: The gatsby and gatsby-source-medium packages in examples/using-medium/package.json have been upgraded from version ^2.0.0 to ^5.14.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 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, addresses security vulnerabilities by upgrading gatsby and gatsby-source-medium from version 2 to version 5. While fixing the vulnerabilities is important, this is a major version upgrade that introduces significant breaking changes which are not addressed in this PR. The application will not work without further modifications. Most critically, Gatsby v5 requires React 18, but the project is still configured to use React 16. This will cause the build to fail. I've left a specific comment detailing this and other likely issues related to breaking API changes that will need to be addressed.

[gemini-code-assist]

This major version upgrade for gatsby from v2 to v5 requires an update to its peer dependencies. Gatsby v5 requires React 18, but the react and react-dom dependencies in this project are still on version 16. This will break the application. You will need to update react and react-dom to a compatible version (e.g., ^18.2.0).

Additionally, this large version jump for both gatsby and gatsby-source-medium likely includes breaking API changes. The existing code, such as gatsby-config.js and GraphQL queries, will probably need to be migrated to work with the new versions.