[Snyk] Fix for 2 vulnerabilities

[mnk-blr]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-15309438	170
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AJV-15274295	156

---

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)

[mnk-blr]

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

Status	Scanner	Critical	High	Medium	Low	Total (19)
⛔	Open Source Security	2	17	0	0	19 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.

[claude]

🚨 Breaking Change - ESLint v9 Migration Required

This upgrade from ESLint v8 to v9 introduces breaking changes that require configuration updates:

1. Flat Config Migration: ESLint v9 uses flat config as default. The current .eslintrc.* files need migration to eslint.config.js
2. Removed Rules: Several rules have been removed or deprecated
3. Plugin Compatibility: Some ESLint plugins may not be compatible with v9

Required Actions:

• Migrate from .eslintrc.js to eslint.config.js flat config format
• Update or replace incompatible plugins
• Test all lint rules still work as expected
• Update CI/build scripts if they depend on specific ESLint behavior

Risk: This change will likely break the current lint configuration and CI pipeline.

[claude]

⚠️ Major Version Update

eslint-import-resolver-typescript v2→v3 may have breaking changes. Verify import resolution still works correctly with the existing TypeScript configuration.

[claude]

🚨 Breaking Change - Jest v29 Migration Required

Jest v27→v29 includes significant breaking changes that require migration:

Key Breaking Changes:

• Default test environment changed from node to jsdom
• jest.resetModules() behavior changes
• Some APIs removed (e.g., jest.setTimeout() moved to jest.setSystemTime())
• testURL option removed

Required Actions:

• Update Jest configuration to specify test environment explicitly
• Review and update any tests using deprecated APIs
• Test all existing test suites still pass
• Update any Jest-related scripts or CI configuration

Risk: Tests may fail after this upgrade without proper migration.

[claude]

PR Review Summary

⚠️ NOT READY FOR MERGE

While this Snyk security fix addresses critical ReDoS vulnerabilities (minimatch & ajv), it introduces breaking changes that require additional work before merging.

Critical Issues Found:

🚨 ESLint v8→v9 Breaking Changes

• Requires migration from .eslintrc.* to flat config (eslint.config.js)
• Multiple plugins may be incompatible with v9
• Will break current lint pipeline

🚨 Jest v27→v29 Breaking Changes

• Default test environment changes
• API deprecations and removals
• May break existing test suites

⚠️ Additional Updates Needed

• eslint-import-resolver-typescript v2→v3 (potential breaking changes)
• Various transitive dependency updates with potential compatibility issues

Recommended Actions Before Merge:

1. ESLint Migration: Update configuration to flat config format
2. Jest Migration: Review/update test configurations and deprecated API usage
3. Testing: Run full test suite to verify compatibility
4. CI Verification: Ensure build pipeline works with new dependency versions
5. Plugin Compatibility: Verify all ESLint plugins work with v9

Security Value:

✅ Fixes high-severity ReDoS vulnerabilities (scores 170 & 156)

Recommendation: Address breaking changes before merging, or consider a smaller targeted security fix for the immediate vulnerabilities.