Help reduce the likelihood/effects of attempted ReDoS #83
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.
I've seen that the likelihood of ReDoS has come up a few times in this repo before and agree it's not really a major security thing, but it's one of those things that can have a negative impact on high-throughput systems.
This PR suggests a couple of possible ways to limit the effect of these.
This is based partly on some downstream discussion at lovell/sharp#4450
Thank you for all your work continuing to maintain these colo(u)r-related packages.