Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade chai from 4.3.10 to 4.4.1 #91

Closed

Conversation

MaxMood96
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade chai from 4.3.10 to 4.4.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released 2 months ago, on 2024-01-12.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Server-side Request Forgery (SSRF)
SNYK-JS-IP-6240864
537/1000
Why? Proof of Concept exploit, CVSS 8.6
Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
537/1000
Why? Proof of Concept exploit, CVSS 8.6
Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
537/1000
Why? Proof of Concept exploit, CVSS 8.6
Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
537/1000
Why? Proof of Concept exploit, CVSS 8.6
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: chai from chai GitHub release notes
Commit messages
Package name: chai

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Copy link

stale bot commented Jun 8, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We try to do our best, but nock is maintained by volunteers and there is only so much we can do at a time. Thank you for your contributions.

@stale stale bot added the stale label Jun 8, 2024
@stale stale bot closed this Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants