Skip to content

[Snyk] Fix for 1 vulnerabilities#3681

Open
cc-prodsec wants to merge 1 commit intorelease-2.9.xfrom
snyk-fix-feda7799fcfd86c1f979814d70d02a0a
Open

[Snyk] Fix for 1 vulnerabilities#3681
cc-prodsec wants to merge 1 commit intorelease-2.9.xfrom
snyk-fix-feda7799fcfd86c1f979814d70d02a0a

Conversation

@cc-prodsec
Copy link
Collaborator

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/internal-lib-build/package.json
  • packages/internal-lib-build/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-MINIMATCH-15309438
  828  

Breaking Change Risk

Merge Risk: High

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:

🦉 Regular Expression Denial of Service (ReDoS)

…-build/package-lock.json to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-MINIMATCH-15309438
@cc-prodsec
Copy link
Collaborator Author

Merge Risk: High

This upgrade includes multiple major versions for critical development tools like ESLint, Jest, and Rimraf, introducing significant breaking changes that require developer action. The most impactful changes are the mandatory migration to ESLint's new "flat" configuration format, fundamental API changes in Jest, and the conversion of several packages to ES Modules, which breaks existing require() statements.

Top 3 Most Impactful Upgrades

1. eslint 7.32.010.0.0 (HIGH RISK)

This is a multi-major version upgrade that completely overhauls ESLint's configuration system.

  • Mandatory Flat Config: The traditional .eslintrc.js file is no longer supported in v10. You must migrate to the new eslint.config.js (flat config) format.
  • Node.js Version: Support for Node.js versions below 20.19.0 has been dropped.
  • Removed Functionality: Numerous formatters, core rules (require-jsdoc, valid-jsdoc), and the CLIEngine class have been removed.

Recommendation: This is a significant migration effort. Follow the official ESLint Migration Guide to update your configuration files and rules before merging.

2. jest & jest-cli 26.6.329.0.0 (HIGH RISK)

This upgrade spans three major versions (v27, v28, v29) with several breaking changes to test setup and APIs.

  • Dependencies and Defaults: jest-environment-jsdom is no longer a default dependency and must be installed explicitly. The default test environment is now node. jest-circus is the new default test runner.
  • API and Config Changes: Several configuration options have been renamed (e.g., testURL is removed). The expect utility is now a named export (import {expect} from 'expect'). The behavior of toHaveProperty is stricter.
  • Node.js Version: Support for Node.js 12 and 17 has been dropped.

Recommendation: You will need to install jest-environment-jsdom manually, update your Jest configuration for renamed options, and potentially refactor test files for API changes.

3. rimraf 2.7.16.1.1 (HIGH RISK)

This upgrade introduces fundamental API and module system changes.

  • ES Module Conversion: The package is now an ES Module. CommonJS require('rimraf') will fail. You must switch to import { rimraf } from 'rimraf'.
  • Promise-Based API: The function no longer accepts a callback and instead returns a Promise.

Recommendation: Update all require('rimraf') statements to use ES Module imports

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

@cc-prodsec cc-prodsec requested a review from a team as a code owner February 20, 2026 14:33
@cc-prodsec
Copy link
Collaborator Author

cc-prodsec commented Feb 20, 2026

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

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants