[Snyk] Upgrade jimp from 0.6.1 to 0.22.12

[nejidevelops]

Snyk has created this PR to upgrade jimp from 0.6.1 to 0.22.12.

ℹ️ 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 206 versions ahead of your current version.

• The recommended version was released a year ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Denial of Service (DoS) SNYK-JS-JPEGJS-2859218	696	Proof of Concept
	Denial of Service (DoS) SNYK-JS-JPEGJS-570039	696	No Known Exploit
	Prototype Pollution SNYK-JS-MINIMIST-559764	696	Proof of Concept
	Exposure of Sensitive Information to an Unauthorized Actor SNYK-JS-PHIN-6598077	696	No Known Exploit
	Prototype Pollution SNYK-JS-MINIMIST-2429795	696	Proof of Concept

---

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:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gemini-code-assist]

Summary of Changes

Hello @nejidevelops, 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 performs a substantial upgrade of the jimp image processing library from version 0.6.1 to 0.22.12. The primary motivation for this update is to mitigate several identified security vulnerabilities, including various Denial of Service and Prototype Pollution issues. This change impacts the project's dependency tree significantly, updating numerous related @jimp packages and introducing new ones, while also removing some outdated dependencies.

Highlights

• Major Dependency Upgrade: The jimp image processing library has been upgraded from version 0.6.1 to 0.22.12, a significant jump of 206 versions.
• Security Vulnerability Fixes: This upgrade directly addresses several critical security vulnerabilities, including Denial of Service (DoS), Prototype Pollution, and Exposure of Sensitive Information to an Unauthorized Actor, as identified by Snyk.
• Expanded Dependency Ecosystem: The update involves extensive changes to the dependency tree, including upgrades to numerous @jimp sub-packages (e.g., @jimp/bmp, @jimp/core, @jimp/plugins) and the introduction of new direct and transitive dependencies such as isomorphic-fetch and gifwrap.
• Dependency Streamlining: Older dependencies like @babel/polyfill and core-js have been removed as direct requirements from several jimp-related modules, streamlining the dependency graph.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades the jimp package from version 0.6.1 to 0.22.12. This is a significant upgrade that resolves multiple security vulnerabilities. While the dependency upgrade is beneficial, the changes to package-lock.json indicate a switch in the package registry from a private Nexus repository (nexus.solutions.consensys-uk.net) to the public npm registry (registry.npmjs.org) for many packages. This is a critical change that could potentially break your build pipeline or violate internal policies. It is highly recommended to verify this change and, if necessary, regenerate the package-lock.json file using your project's intended npm registry configuration.

[gemini-code-assist]

This pull request changes the package registry source from your private Nexus repository (nexus.solutions.consensys-uk.net) to the public npm registry (registry.npmjs.org) for this package and many others. This was likely caused by the automated tool running with a default npm configuration. This change could break your CI/CD pipeline if it relies on the private registry, or if it violates your organization's policies for package sources. Please ensure this change is intentional. If not, you should regenerate the package-lock.json file by running npm install with your npm client configured to use the correct private registry.