Skip to content

[Snyk] Fix for 2 vulnerabilities - #180

Open
saumilmac wants to merge 1 commit into
masterfrom
snyk-fix-c444e12ccb15bda60207fc5e0c99351c
Open

[Snyk] Fix for 2 vulnerabilities#180
saumilmac wants to merge 1 commit into
masterfrom
snyk-fix-c444e12ccb15bda60207fc5e0c99351c

Conversation

@saumilmac

Copy link
Copy Markdown
Owner

snyk-top-banner

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
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-BRACEEXPANSION-18313044
  828  
high severity Inefficient Algorithmic Complexity
SNYK-JS-JSYAML-18313070
  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:

🦉 Allocation of Resources Without Limits or Throttling

@saumilmac

Copy link
Copy Markdown
Owner Author

Merge Risk: High

This release includes several major version upgrades with significant breaking changes. The upgrades for glob and js-yaml are high-risk and will require code modifications. Other upgrades introduce environment changes, such as dropping support for older Node.js versions.

Top 3 Most Impactful Upgrades

  • glob 7.2.012.0.0 (High Risk): This is a substantial upgrade across multiple major versions (v8, v9, v10, v11, v12) that introduces numerous breaking changes requiring developer action.
    • API Rewrite: The API has been completely rewritten. It now uses Promises instead of callbacks, and function names have changed. [3]
    • ESM and Exports: Version 10 and later use named exports only; there is no default export. [3]
    • Path Separators: Since v8, backslashes (\) are treated exclusively as escape characters. All glob patterns, including on Windows, must use forward slashes (/). [3, 11, 12]
    • **Node.js Requirement

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