Repository navigation
Conversation
express 5.2.1 asks for proxy-addr ^2.0.7, so the lockfile kept 2.0.7, which carries a critical advisory fixed in 2.0.8. An override floor holds it there, as the other security floors do.
Contributor
Author
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
1 participant
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.
bun.lockresolvesproxy-addr2.0.7, which carries the critical advisory GHSA-jqcg-44mw-7w3h. The fix is in 2.0.8. It comes in through express 5.2.1, whose^2.0.7range lets the lockfile stay on 2.0.7.This adds
proxy-addrto the security override floors inpackage.json, next to undici, hono, ws and fast-uri. 2.0.8 is past the seven-day install age gate. The lockfile is regenerated with the pinned Bun 1.4.2, so it stays at lockfile version 1.