Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
cmaster11
reviewed
Sep 5, 2025
package.json
Outdated
| "got": "^11.8.6", | ||
| "minimist": "^1.2.8", | ||
| "parallel-stream": "^1.1.2", | ||
| "safe-regex": "^2.1.1", |
There was a problem hiding this comment.
Hmmm safe-regex is an unmaintained package (6yo last commit). Should we be using maybe https://github.com/fastify/safe-regex2 ?
Contributor
Author
There was a problem hiding this comment.
Good call - swapped for safe-regex2!
cmaster11
approved these changes
Sep 5, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
As per a HackerOne report - this adds
safe-regexand a check for max line length to prevent a potential ReDoS from malicious inputs/regexes when using this package. Tested locally with test data from the command line, confirmed that the new error cases both throw as expected and the options otherwise work.