[Snyk] Upgrade jimp from 0.6.8 to 0.22.12

[nejidevelops]

Snyk has created this PR to upgrade jimp from 0.6.8 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 193 versions ahead of your current version.

• The recommended version was released 2 years 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-MINDOCUMENT-13045385	696	Proof of Concept
	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-XML2JS-5414874	696	Proof of Concept
	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, automatically generated by Snyk, focuses on a critical security and maintenance update for the jimp image processing library. By upgrading jimp and its associated sub-dependencies to their latest versions, the project significantly enhances its security posture by patching several known vulnerabilities, including Denial of Service and Prototype Pollution. This ensures the application benefits from the most recent stability improvements and security patches available for its image handling capabilities.

Highlights

• Dependency Upgrade: The jimp package has been upgraded from version 0.6.8 to 0.22.12 to address multiple security vulnerabilities and keep the project dependencies up-to-date. This is a significant jump, spanning 193 versions.
• Security Fixes: This upgrade resolves several security issues, including high-severity Denial of Service (DoS) vulnerabilities (SNYK-JS-JPEGJS-2859218, SNYK-JS-JPEGJS-570039), medium-severity Prototype Pollution issues (SNYK-JS-MINDOCUMENT-13045385, SNYK-JS-MINIMIST-559764, SNYK-JS-XML2JS-5414874, SNYK-JS-MINIMIST-2429795), and a medium-severity Exposure of Sensitive Information vulnerability (SNYK-JS-PHIN-6598077).
• Sub-dependency Updates: Numerous @jimp/* sub-packages and other related dependencies like file-type, follow-redirects, jpeg-js, load-bmfont, min-document, phin, pngjs, and utif (now utif2) have also been updated to their latest compatible versions, reflecting a comprehensive refresh of the image processing library's ecosystem.
• New Dependencies: New dependencies such as @jimp/plugin-circle, @jimp/plugin-fisheye, @jimp/plugin-shadow, @jimp/plugin-threshold, gifwrap, centra, isomorphic-fetch, and whatwg-fetch have been introduced as part of the jimp upgrade, indicating potential new features or internal architectural changes within the library.

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

[gemini-code-assist]

Code Review

This pull request upgrades jimp from version 0.6.8 to 0.22.12, which is a necessary update to fix several security vulnerabilities. However, this is a very large version jump that includes numerous significant breaking changes. The most important one is the complete transition from a callback-based API to a Promise-based API in jimp@0.9.0. This means any part of the application using jimp with callbacks will break and needs to be refactored to use Promises or async/await. Due to the high risk of runtime failures, this PR should not be merged without updating the application code to be compatible with the new jimp version and conducting thorough testing.

[gemini-code-assist]

This upgrade from jimp@^0.6.4 to ^0.22.12 is a major version jump that introduces significant breaking changes, which will likely cause runtime failures in the application.

The most critical change, introduced in jimp@0.9.0, is the switch from a callback-based API to a Promise-based API. All asynchronous operations now return Promises.

For example, code that previously looked like this:

Jimp.read('image.png', (err, image) => {
  if (err) throw err;
  image.resize(256, 256).write('resized.png');
});

will need to be refactored to use Promises, for example with async/await:

async function processImage() {
  try {
    const image = await Jimp.read('image.png');
    await image.resize(256, 256).writeAsync('resized.png');
  } catch (err) {
    console.error(err);
  }
}

Other breaking changes across these versions include:

• Many static methods like jimp.loadFont, jimp.create, and jimp.read have been changed.
• The way image manipulation methods are chained might have changed, and methods like write now have an async counterpart (writeAsync).
• Node.js version support has been updated, dropping support for older versions.

The application code that relies on jimp must be carefully reviewed and updated to align with the new API. Without these changes, this upgrade will break the application.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Upgrading Jimp without updating import path will break Lambda build

Bumping Jimp from ^0.6.4 to ^0.22.12 is a major jump and the library is now an ESM package that no longer exposes the jimp/es entry used by src/lambda/s3/resizeImage.ts. When the Lambda is compiled the build will attempt to resolve jimp/es and fail with Cannot find module 'jimp/es', preventing the SNS handler from deploying. The upgrade needs a code change to import from jimp (and adjust for the ESM export) before this dependency change can be safely applied.

Useful? React with 👍 / 👎.