[Snyk] Fix for 2 vulnerabilities

[snyk-io]

Snyk has created this PR to fix 2 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
	Inefficient Algorithmic Complexity SNYK-JS-BRACEEXPANSION-17706650
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-17342520

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:

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

---

This change is 

[snyk-io]

This update includes major versions for eslint and jest, introducing significant breaking changes that require developer action.

Top 3 Most Impactful Upgrades

• eslint 8.57.1 → 10.0.0 (High Risk): This upgrade spans two major versions (v9 and v10) and introduces substantial breaking changes. The legacy .eslintrc configuration format is completely removed in v10.0.0. [1, 6] All projects must migrate to the new flat eslint.config.js format. [4, 5] Additionally, support for Node.js versions below 20.19.0 is dropped. [1, 2]

  • Recommendation: Before merging, you must migrate your ESLint configuration to the flat config format. This is a mandatory change. Verify your CI environment is using a compatible Node.js version.

• jest 29.7.0 → 30.0.0 (Medium Risk): This major version drops support for Node.js 14, 16, 19, and 21, requiring at least Node.js 18. [3, 12] It also upgrades its jsdom dependency, which may affect DOM-related tests, and removes several deprecated expect aliases. [3, 8] Snapshots may require updating due to formatting changes. [3]

  • Recommendation: Ensure your environment runs a supported Node.js version (18+). After upgrading, run tests and update any failing snapshots or tests that used removed aliases.

• @actions/glob 0.5.1 → 0.7.0 (Low Risk): This is a minor version update. There are no documented breaking changes between these versions. [16, 17] This upgrade is considered safe for typical usage.

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: c2ec0ac

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[snyk-io]

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

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

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

[snyk-io]

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

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

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

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[kilo-code-bot]

WARNING: package-lock.json not synchronized with package.json

package.json was modified but package-lock.json was not regenerated. This leaves the lockfile out of sync and will cause installation or CI failures.

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

CRITICAL: ESLint 10 drops .eslintrc.* configuration support

This project's .eslintrc.js and lint script (eslint --config ./.eslintrc.js) will break after upgrading to ESLint 10, which completely removes support for .eslintrc.* files. A migration to eslint.config.js flat config format is required before this dependency can be safely upgraded. Without this migration, npm run lint will fail.

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

WARNING: Jest 30 has stale peer dependencies

jest-circus (29.7.0), jest-each (29.7.0), and ts-jest (29.4.1) remain at v29 while jest jumps to v30. Jest 30 introduced breaking changes that may cause test failures or runtime errors. These related packages should be updated to their Jest 30-compatible versions.

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

Code Review Summary

Status: 3 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	1
WARNING	2
SUGGESTION	0

Issue Details (click to expand)

CRITICAL

File	Line	Issue
package.json	48	ESLint 10 drops .eslintrc.* support, breaking the lint script

WARNING

File	Line	Issue
package.json	35	package-lock.json out of sync
package.json	52	Jest 30 has stale peer dependencies

Files Reviewed (1 files)

• package.json - 3 issues

Fix these issues in Kilo Cloud

---

_{Reviewed by step-3.7-flash-20260528 · Input: 82.1K · Output: 17.9K · Cached: 334.3K}