Skip to content

[Snyk] Fix for 9 vulnerabilities#148

Open
jhamot wants to merge 1 commit intomasterfrom
snyk-fix-2e2541597054cc5c9feab65ee35492c0
Open

[Snyk] Fix for 9 vulnerabilities#148
jhamot wants to merge 1 commit intomasterfrom
snyk-fix-2e2541597054cc5c9feab65ee35492c0

Conversation

@jhamot
Copy link
Owner

@jhamot jhamot commented Feb 22, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • script/package.json
  • script/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Code Injection
SNYK-JS-LODASH-1040724
  398  
high severity Prototype Pollution
SNYK-JS-LODASH-567746
  317  
high severity Prototype Pollution
SNYK-JS-LODASH-6139239
  267  
high severity Prototype Pollution
SNYK-JS-LODASH-450202
  254  
high severity Prototype Pollution
SNYK-JS-LODASH-608086
  250  
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-MINIMATCH-15309438
  170  
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-AJV-15274295
  156  
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  144  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-LODASH-1018905
  104  

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)
🦉 Code Injection
🦉 Prototype Pollution

@jhamot
Copy link
Owner Author

jhamot commented Feb 22, 2026

Merge Risk: High

This upgrade involves multiple high-risk major version updates for critical linting and transpilation packages. Significant configuration changes and code modifications are required.

Highlights & Recommendations

  • eslint 5.16.0 → 9.0.0 (HIGH RISK)
    This is a substantial upgrade spanning four major versions. The most critical breaking change is in v9.0.0, which introduces a new default configuration format.

    • Action Required: You must migrate your .eslintrc configuration file to the new eslint.config.js ("flat config") format. ESLint provides a migration guide to assist with this process.
    • Environment: Support for Node.js versions below 18.18.0 has been dropped.
    • Other Changes: Numerous rules and formatters have been removed or updated across versions 6, 7, 8, and 9.
  • babel-core 5.8.38 → 6.10.4 (HIGH RISK)
    Babel 6 introduced a fundamental architectural shift. Out of the box, it no longer performs any code transformations.

    • Action Required: You must explicitly install and configure plugins or presets (e.g., babel-preset-es2015) to enable transformations. This is typically done in a .babelrc file.
    • Configuration: The babel npm package is deprecated and replaced by babel-cli and babel-core. Your build scripts and dependencies will need to be updated accordingly.
  • babel-eslint 10.0.1 → 10.1.0 (MEDIUM RISK)
    While this is a minor version update, the babel-eslint package is deprecated and will no longer receive updates.

    • Recommendation: Migrate from babel-eslint to its replacement, @babel/eslint-parser, to ensure you continue to receive updates and bug fixes.

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants