Repository navigation
fix(deps): pin ip-address zone-validation patch - #40
Merged
Merged
Conversation
|
Warning Review limit reachedEnable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Next included review available in 17 minutes. View limit details
Comment |
This was referenced Oct 24, 2026
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.
Advisory chain
Pins the rate-limiter transitive
ip-addressdependency to exactly10.7.4, addressing GHSA-rxp7-6hxx-x8q5 without changing the existing IPv6/56grouping policy.Verification
10.7.2;10.7.4passes.ed75493and its thread resolved.ip-addressdependency selected by the limiter, not a root-level hoisted or duplicate dev-only copy. Restoring only the subprocess's bare import is detected by a negative control.Integration
PR #38 already includes this commit together with the separate
follow-redirectsadvisory fix. Its combined production audit has zero advisories. The base lockfile still contains the other vulnerable transitive, so do not treat this standalone branch as a complete production dependency remediation. A fresh standalone production audit still reports one highfollow-redirectsvulnerability.PARKED for the coordinated merge: the current head
ed75493is contained in #38 at464835d, where the production audit is clean. Once #38 passes its outstanding runtime/proxy/token and restart-state gate, preserve history with a merge commit so this advisory PR can merge indirectly without a partially patched default-branch intermediate.Summary by cubic
Pins the
ip-addresstransitive dependency to exactly10.7.4to fix GHSA-rxp7-6hxx-x8q5 without changing the existing IPv6/56grouping behavior.ip-addressfrom the limiter's own installation to cover nested dependencies.overridesentry inpackage.json.Note: this branch alone is not a complete production remediation—the base lockfile still contains the vulnerable
follow-redirectstransitive. PR #38 combines both fixes.Written for commit ed75493. Summary will update on new commits.