Repository navigation
fix(deps): patch body-parser advisory GHSA-27r3-jxmh-p828 - #142
Merged
Merged
Conversation
express 4.22.3 is already the latest 4.x and its ~1.20.5 range admits the patched 1.20.9, so a lockfile refresh fixes it without the express 5 major bump in #137.
🟢 Tier S · Ready to merge
The lockfile updates the transitive
📂 Walkthrough · 1
Reviewed |
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
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.
Fixes Dependabot alert GHSA-27r3-jxmh-p828 (high): body-parser < 1.20.9, pulled in transitively by express.
express 4.22.3 is already the latest 4.x release and depends on `body-parser ~1.20.5`, which admits the patched 1.20.9. So this only refreshes the lockfile (`npm update body-parser --package-lock-only`): body-parser 1.20.8 -> 1.20.9. No overrides and no express 5 major bump (the alternative in #137).
Verification: `npm ls body-parser` shows only `express@4.22.3 -> body-parser@1.20.9`, `npm audit` reports 0 vulnerabilities, and an `npm ci` install served a JSON POST through `express.json()` correctly.