[Snyk] Security upgrade @typescript-eslint/eslint-plugin from 4.27.0 to 5.10.0

[hashim21223445]

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

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Malicious Package SNYK-JS-DEBUG-12552895

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
package.json	37% smaller

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[gemini-code-assist]

Summary of Changes

Hello @hashim21223445, 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 by upgrading a key development dependency, @typescript-eslint/eslint-plugin. This update resolves a critical 'Malicious Package' vulnerability, ensuring the project's codebase remains secure. Reviewers should note the need for a manual update to package-lock.json to fully incorporate these security improvements.

Highlights

• Security Upgrade: This pull request introduces a security upgrade for the @typescript-eslint/eslint-plugin dependency to address a critical vulnerability.
• Dependency Version Update: The @typescript-eslint/eslint-plugin package has been updated from version ^4.8.1 to ^5.10.0 in package.json.
• Vulnerability Fixed: The upgrade specifically fixes the 'Malicious Package' vulnerability identified as SNYK-JS-DEBUG-12552895.
• Manual Action Required: The package-lock.json file was not automatically updated and requires manual intervention to reflect the new dependency version before merging.

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 @typescript-eslint/eslint-plugin to resolve a security vulnerability. This is a necessary update. I've identified a critical issue with this change: upgrading @typescript-eslint/eslint-plugin to a new major version (v5) requires a corresponding upgrade of @typescript-eslint/parser to v5 to maintain compatibility. I've left a specific comment with a code suggestion to address this. Additionally, as the Snyk bot noted, the lock file needs to be updated. Since this project uses yarn (via jlpm), you should run jlpm install to update yarn.lock and commit the changes. It would also be beneficial to remove the package-lock.json file to prevent future inconsistencies.

[gemini-code-assist]

Upgrading @typescript-eslint/eslint-plugin to a new major version (v5) requires a corresponding major version upgrade for @typescript-eslint/parser. The v5 packages of @typescript-eslint have a peer dependency on each other. Without this change, your linting setup will likely break.

Suggested change

	"@typescript-eslint/eslint-plugin": "^5.10.0",
	"@typescript-eslint/parser": "^4.33.0",
	"@typescript-eslint/eslint-plugin": "^5.10.0",
	"@typescript-eslint/parser": "^5.10.0",