[Snyk] Security upgrade eslint from 6.6.0 to 10.0.0

[Seismic-Security-Service]

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

Snyk changed the following file(s):

• pkgs/eslint-plugin/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
	Allocation of Resources Without Limits or Throttling SNYK-JS-JSYAML-19496768	169

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Allocation of Resources Without Limits or Throttling

[Seismic-Security-Service]

This upgrade from ESLint v6.6.0 to v10.0.0 is a high-risk migration involving multiple major versions and significant, mandatory breaking changes. The most critical change is the complete removal of the legacy .eslintrc configuration system in favor of the new eslint.config.js (flat config) format.

Key Breaking Changes & Actions Required:

• Configuration System Overhaul: The .eslintrc and .eslintignore file formats are no longer supported as of v10. You must migrate your configuration to the new eslint.config.js flat config format. ESLint provides a migration tool to assist with this process.
• Node.js Version: Support for older Node.js versions has been progressively dropped. ESLint v10 requires Node.js v20.19.0 or higher. You must ensure your development and CI/CD environments meet this requirement.
• API and Rule Changes:
  • The CLIEngine class was deprecated in v7 and removed in v8, replaced by the asynchronous ESLint class.
  • Many rules have been removed from the core and moved to plugins (e.g., Node.js/CommonJS rules moved to eslint-plugin-node in v7).
  • The valid-jsdoc and require-jsdoc rules were removed in v9.
  • The eslint:recommended configuration has been updated across multiple major versions, which may introduce new linting errors.
• Plugin and Tooling Compatibility: You must update all ESLint plugins, parsers (like @typescript-eslint/parser), and related tooling to versions compatible with ESLint v10 and its flat config system.

Recommendation: This is a major refactoring effort that requires careful planning. Do not merge this upgrade without completing the migration. It is strongly advised to follow the official migration guides for each major version (v7, v8, v9, v10) to understand the full scope of changes.

Sources:

• ESLint v10 Migration Guide
• ESLint v9 Migration Guide
• ESLint v8 Migration Guide
• ESLint v7 Migration Guide

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[Seismic-Security-Service]

⛔ Snyk checks have failed. 20 issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (20)
⛔	Open Source Security	1	19	0	0	20 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.