chore: bump path-to-regexp dependency to 0.1.10 #147
Closed
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
The current version of path-to-regexp has a [CVE](GHSA-9wv6-86v2-598j) open and causes audit warnings in downstream consumers of this package. Upgrade to v0.10.0 as recommended in the advisory. Tested on node v18.20.5
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/[email protected] |
bjohansebas
reviewed
Nov 20, 2024
| @@ -13,7 +13,7 @@ | |||
| "debug": "2.6.9", | |||
| "methods": "~1.1.2", | |||
| "parseurl": "~1.3.3", | |||
| "path-to-regexp": "0.1.7", | |||
| "path-to-regexp": "0.1.10", | |||
There was a problem hiding this comment.
Suggested change
| "path-to-regexp": "0.1.10", | |
| "path-to-regexp": "0.1.11", |
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.
The current version of path-to-regexp has a CVE open and causes audit warnings in downstream consumers of this package.
Upgrade to v0.10.0 as recommended in the advisory.
Tested on node v18.20.5.