Skip to content

[Snyk] Upgrade request from 2.88.0 to 2.88.2#124

Open
Dids wants to merge 1 commit into
masterfrom
snyk-upgrade-c054624c8f755c6428b782816e1cd26a
Open

[Snyk] Upgrade request from 2.88.0 to 2.88.2#124
Dids wants to merge 1 commit into
masterfrom
snyk-upgrade-c054624c8f755c6428b782816e1cd26a

Conversation

@Dids
Copy link
Copy Markdown
Contributor

@Dids Dids commented Nov 23, 2023

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


Snyk has created this PR to upgrade request from 2.88.0 to 2.88.2.

ℹ️ 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 1 version ahead of your current version.
  • The recommended version was released 4 years ago, on 2020-02-11.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Regular Expression Denial of Service (ReDoS)
SNYK-JS-WS-1296835
586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Proof of Concept

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

Release notes
Package name: request from request GitHub release notes

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

@stale
Copy link
Copy Markdown

stale Bot commented May 21, 2026

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale Bot added the wontfix Issues that will not be fixed. label May 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wontfix Issues that will not be fixed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants