chore: upgrade follow-redirects package in order to fix security vulnerability #1660
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GuusDeGraeve
changed the title
This was referenced Feb 23, 2024
|
@jcrugzz would you have the time to look at this PR and possibly include it in a new release? The dependency is vulnerable and since this package is a sub dependency of many, it is "blocking" upgrades and forcing manual overrides (not ideal). |
|
This project node-http-proxy hasn't had any activity or maintenance at all in over 4 years, but has 98 open pull requests and about 15 million downloads per week. Is anybody thinking of taking over and doing some basic maintenance? (I love and greatly appreciate this package and use it all the time.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Versions of the follow-redirects package prior to version 1.15.4 are vulnerable to improper input validation. This PR upgrades the dependency, without changing the lockfile version.
See CVE-2023-26159
This should fix #1657