Skip to content

[Snyk] Fix for 7 vulnerabilities#115

Open
jhamot wants to merge 1 commit intomasterfrom
snyk-fix-1ce615c0623b2c923d715500e197752b
Open

[Snyk] Fix for 7 vulnerabilities#115
jhamot wants to merge 1 commit intomasterfrom
snyk-fix-1ce615c0623b2c923d715500e197752b

Conversation

@jhamot
Copy link
Owner

@jhamot jhamot commented Nov 14, 2025

snyk-top-banner

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

Snyk changed the following file(s):

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

Merge Risk: High

This upgrade contains significant breaking changes, primarily from the eslint package update from v5 to v9. The eslint upgrade introduces a new default configuration format, drops support for older Node.js versions, and removes core rules. The babel-eslint package is deprecated and should be replaced.

Highlights:

  • eslint 5.16.0 → 9.0.0 (High Risk): This major upgrade requires a configuration migration from .eslintrc to the new eslint.config.js flat format. Support for Node.js versions below 18.18.0 has been dropped. The CLIEngine class was removed in v8, replaced by an async ESLint class. Many core rules, including formatting rules, have been removed or deprecated across versions.
  • babel-eslint 10.0.1 → 10.1.0 (Medium Risk): This package is deprecated and has been replaced by @babel/eslint-parser. While this minor update itself is low risk, continued use of the deprecated package is not recommended. You should migrate to the new package.
  • stylelint 9.3.0 → 12.0.0 (Low Risk): This upgrade drops support for Node.js 8.x (in v13, which is outside this range but good to know) and updates glob pattern syntax to only use forward-slashes (/). Most changes involve new rules and options rather than significant API breakage within this version range.

Recommendation: This upgrade requires significant developer effort. Prioritize migrating the ESLint configuration to the new flat format (eslint.config.js) and replacing the deprecated babel-eslint package. Thoroughly test the new linting rules and configurations before merging.

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


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
  256  
high severity Prototype Pollution
SNYK-JS-LODASH-608086
  250  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-LODASH-1018905
  104  
medium severity Prototype Pollution
SNYK-JS-JSYAML-13961110
  50  

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:

🦉 Prototype Pollution
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Code Injection

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