Skip to content

[Snyk] Fix for 1 vulnerabilities#25

Open
CryptoJones wants to merge 1 commit into
masterfrom
snyk-fix-e3daa3bdea482d5fcebf3fbea0661cd9
Open

[Snyk] Fix for 1 vulnerabilities#25
CryptoJones wants to merge 1 commit into
masterfrom
snyk-fix-e3daa3bdea482d5fcebf3fbea0661cd9

Conversation

@CryptoJones
Copy link
Copy Markdown
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • package.json
⚠️ Warning
Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-14724253
  828  

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

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-QS-14724253
@CryptoJones
Copy link
Copy Markdown
Owner Author

CryptoJones commented May 15, 2026

Triage note (#30): Generic "Fix for 1 vulnerabilities" title — no in-title dep info. Recent (Jan 2026), likely still applicable. Quick diff review needed to identify which dep is being bumped before merging.


Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/

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