[Snyk] Security upgrade eslint from 8.18.0 to 9.15.0

[nn6n]

Snyk has created this PR to fix 3 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	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-CROSSSPAWN-8303230	756
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	631
	Regular Expression Denial of Service (ReDoS) SNYK-JS-WORDWRAP-3149973	506

---

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:

🦉 Regular Expression Denial of Service (ReDoS)

[restack-app]

No applications have been configured for previews targeting branch: main. To do so go to restack console and configure your applications for previews.

[gemini-code-assist]

Hello @nn6n, 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!

Summary of Changes

Hello team, gemini-code-assist here providing a summary of this pull request. This PR, automatically generated by Snyk, aims to address three identified vulnerabilities (one high, one medium, and one low severity) by upgrading the eslint dependency. The primary change involves updating the version of eslint in the devDependencies section of the package.json file from 8.18.0 to 9.15.0. Please note the warning from Snyk indicating that the package-lock.json file was not automatically updated and will require a manual update before merging.

Highlights

• Security Upgrade: This PR is a security fix generated by Snyk to address three vulnerabilities (SNYK-JS-CROSSSPAWN-8303230, SNYK-JS-INFLIGHT-6095116, SNYK-JS-WORDWRAP-3149973) by upgrading a dependency.
• Dependency Version Bump: The eslint dependency in devDependencies has been upgraded from version 8.18.0 to 9.15.0.
• Automated PR: This pull request was automatically created by Snyk.
• Manual Step Required: The package-lock.json file was not updated automatically and needs to be updated manually before this PR can be merged.

Changelog

• package.json
  • Updated the eslint dependency version in devDependencies from 8.18.0 to 9.15.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 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 is currently in preview and 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 to provide feedback.

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.

---

A version bumped high,
Security flaws now fly,
Lock file needs a hand.

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 Snyk pull request proposes an upgrade of eslint from version 8.18.0 to 9.15.0. This is a valuable change as it aims to fix three security vulnerabilities, including one high-severity issue.

However, there are a couple of important points to address before this PR can be merged:

1. Critical: package-lock.json Not Updated: As highlighted in the PR description's warning, the package-lock.json file failed to update. This is a critical issue that must be resolved manually. Without an updated lock file, the intended security fixes might not be applied correctly, and builds can become inconsistent.
2. ESLint Major Version Upgrade: The upgrade from ESLint v8 to v9 is a major version change. Snyk's metadata also indicates isBreakingChange:true. Major versions can introduce breaking changes to ESLint configurations, rules, or plugin compatibility. Thorough testing is essential after the package-lock.json is updated.

Please address these points, especially the package-lock.json update, before this PR is considered for merging.

Summary of Findings

• Critical: package-lock.json Not Updated: The package-lock.json file was not automatically updated by Snyk, as stated in the PR's warning. This is a critical issue that must be addressed manually by running npm install (or your project's equivalent command for updating dependencies and the lock file) and committing the updated package-lock.json. Without this, the build may not be reproducible, dependencies might not be resolved as expected, and the intended security fixes might not take effect. This was not commented on directly in the diff as the file is not part of the changes, but it's a critical prerequisite for merging.
• ESLint Major Version Upgrade Requires Testing: The upgrade of ESLint from v8.18.0 to v9.15.0 constitutes a major version change. Such upgrades can introduce breaking changes to ESLint rules, configurations, or plugin compatibility. It's important to thoroughly test the linting process across the codebase after the package-lock.json is correctly updated to ensure no new issues are introduced.

Merge Readiness

This pull request should not be merged in its current state. The primary blocker is the critical issue of the package-lock.json file not being updated. This must be resolved by manually regenerating and committing the lock file.

Once the lock file is corrected, the major version upgrade of ESLint from v8 to v9 also requires careful testing to ensure it doesn't introduce breaking changes to your project's linting setup.

I am unable to approve pull requests. However, I strongly recommend addressing these points—especially the package-lock.json update—before this PR is considered further for merging. Other reviewers should then verify the complete changes.

[gemini-code-assist]

This upgrade to ESLint v9.15.0 is a major version change (from v8.18.0), which Snyk's metadata also flags as a breaking change (isBreakingChange:true). Major versions can introduce incompatibilities with existing configurations, custom rules, or plugins.

Could you please ensure that after updating package-lock.json (which is a critical step, as noted in the general PR feedback), the linting process is thoroughly tested to confirm everything works as expected and that no new linting errors or configuration issues arise?