Skip to content

[Snyk] Security upgrade next from 15.4.2 to 16.1.5#16

Open
dustpan999 wants to merge 2 commits intomainfrom
snyk-fix-1fb97130c870e9fc90b21af309847649
Open

[Snyk] Security upgrade next from 15.4.2 to 16.1.5#16
dustpan999 wants to merge 2 commits intomainfrom
snyk-fix-1fb97130c870e9fc90b21af309847649

Conversation

@dustpan999
Copy link
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-NEXT-15104645
  147  
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-NEXT-15105315
  147  

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

@openzeppelin-code
Copy link

openzeppelin-code bot commented Feb 1, 2026

[Snyk] Security upgrade next from 15.4.2 to 16.1.5

Generated at commit: e72c8ab0226bbf2ff0a5290cd2ee6d1b374ddd26

🚨 Report Summary

Severity Level Results
Contracts Critical
High
Medium
Low
Note
Total
0
0
0
0
0
0
Dependencies Critical
High
Medium
Low
Note
Total
0
0
0
0
0
0

For more details view the full report in OpenZeppelin Code Inspector

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