Skip to content

[Snyk] Fix for 9 vulnerabilities#134

Open
jhamot wants to merge 1 commit intomasterfrom
snyk-fix-930980fb7fdc5769ec19e2b601c25bee
Open

[Snyk] Fix for 9 vulnerabilities#134
jhamot wants to merge 1 commit intomasterfrom
snyk-fix-930980fb7fdc5769ec19e2b601c25bee

Conversation

@jhamot
Copy link
Owner

@jhamot jhamot commented Feb 3, 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

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  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-LODASH-1018905
  104  
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  87  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-MINIMATCH-3050818
  75  
low severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-BRACEEXPANSION-9789073
  57  

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 3, 2026

Merge Risk: High

This upgrade contains a high-risk major version update for npm and a low-risk minor update for a deprecated package.

  • npm 6.14.16 → 11.0.0 (high): This is a significant jump across multiple major versions (v7 through v11), introducing numerous breaking changes. The most critical change is the automatic installation of peer dependencies, which was introduced in v7 and can break existing CI/CD workflows. Subsequent versions dropped support for older Node.js versions (Node < 14 in v9, Node < 16 in v10) and removed several commands like npm bin.

  • babel-eslint 10.0.1 → 10.1.0 (low): This package is deprecated and has been replaced by @babel/eslint-parser. While this specific minor update has no breaking changes, the package will no longer receive updates.

Recommendation: The npm upgrade requires careful validation. Test installation and build processes thoroughly, paying close attention to peer dependency conflicts. Use the --legacy-peer-deps flag as a temporary workaround if needed. Plan to migrate from the deprecated babel-eslint to @babel/eslint-parser.

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