[Snyk] Fix for 10 vulnerabilities

[saurabharch]

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

Snyk changed the following file(s):

• 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
	Improper Handling of Unicode Encoding SNYK-JS-TAR-15038581	713
	Use of a Cryptographic Primitive with a Risky Implementation SNYK-JS-ELLIPTIC-14908844	708
	Arbitrary File Write SNYK-JS-TAR-1579147	639
	Arbitrary File Write SNYK-JS-TAR-1579152	639
	Arbitrary File Write SNYK-JS-TAR-1579155	639
	Arbitrary File Overwrite SNYK-JS-TAR-1536528	624
	Arbitrary File Overwrite SNYK-JS-TAR-1536531	624
	Prototype Pollution SNYK-JS-MINIMIST-559764	601
	Prototype Pollution SNYK-JS-MINIMIST-2429795	506
	Regular Expression Denial of Service (ReDoS) SNYK-JS-TAR-1536758	410

---

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:

🦉 Prototype Pollution
🦉 Arbitrary File Overwrite
🦉 Regular Expression Denial of Service (ReDoS)

[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 resolving 10 identified vulnerabilities in its yarn dependencies. This is achieved through targeted upgrades of specific packages within the package.json file, ensuring the project benefits from the latest security patches.

Highlights

• Vulnerability Fixes: This pull request addresses 10 identified security vulnerabilities within the project's yarn dependencies. These include high-severity issues such as Arbitrary File Write and Arbitrary File Overwrite, as well as medium and low-severity issues like Prototype Pollution, Improper Handling of Unicode Encoding, and Regular Expression Denial of Service (ReDoS).
• Dependency Updates: The package.json file has been updated to upgrade key dependencies. Specifically, gatsby has been updated from 1.0.0-beta.5-alpha.fb30fcd6 to 2.13.79, postcss-inherit from a git URL reference to version 4.1.0, and sharp from 0.19.1 to 0.26.0. These updates are intended to resolve the reported vulnerabilities.
• Manual yarn.lock Update Required: A critical warning indicates that the yarn.lock file failed to update automatically and requires manual intervention before merging. For users leveraging Yarn's zero-install feature, running yarn will also be necessary to update the .yarn/cache/ directory after merging.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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
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 pull request 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 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. ↩

[netlify]

❌ Error Happens

Name	Link
🔨 Latest commit	ca33c84
🔍 Latest deploy log	https://app.netlify.com/projects/wekanhow/deploys/69702ad37eb85b0008dcee95

[gemini-code-assist]

Code Review

This pull request updates several dependencies to address reported vulnerabilities, as indicated by Snyk. Key updates include gatsby from a beta git hash to a stable major version, postcss-inherit from a git dependency to a published package, and sharp to a newer minor version. While these updates are crucial for security, the significant version jumps, especially for gatsby and sharp, warrant thorough testing to ensure no breaking changes or regressions are introduced. Additionally, the yarn.lock file was not updated, which is a critical issue that must be resolved before merging to maintain dependency consistency and reproducible builds.

[gemini-code-assist]

The update of gatsby from a beta git hash (1.0.0-beta.5-alpha.fb30fcd6) to a stable major version (2.13.79) is a significant change. Major version upgrades often introduce breaking changes that could impact the application's functionality. Please ensure that all parts of the application relying on gatsby have been thoroughly tested against this new version to prevent unexpected issues.

[gemini-code-assist]

The sharp dependency has been updated from ^0.19.1 to ^0.26.0. While semver indicates this as a minor version update, sharp often includes significant changes or new features in minor releases due to its native dependencies. It's important to verify that this update does not introduce any regressions or unexpected behavior, especially concerning image processing functionalities.

[gemini-code-assist]

Changing postcss-inherit from a direct git dependency to a published npm package (4.1.0) is a positive change. This improves the stability and reproducibility of dependency resolution, as it relies on a versioned package from the npm registry rather than a specific git commit or branch.