Bump brace-expansion to 5.0.6 to resolve Dependabot alert#987
Merged
Conversation
Resolves a medium-severity DoS advisory where a large numeric range defeats brace-expansion's documented `max` protection (vulnerable < 5.0.6). Bumps the three transitive 5.0.5 entries (via eslint, editorconfig, @eslint/config-array) in the lockfile to 5.0.6. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Summary
Resolves the single open Dependabot alert (#102) — a medium-severity DoS advisory in
brace-expansionwhere a large numeric range defeats the documentedmaxprotection. Affected range is>= 5.0.0, < 5.0.6.brace-expansionis a transitive dependency, pinned at5.0.5in three places in the lockfile (viaeslint,editorconfig, and@eslint/config-array). This bumps those three entries to5.0.6, reusing the resolved URL and integrity hash already present in the lockfile (markdownlint-clialready resolves 5.0.6). The bump satisfies the existing^5.0.5ranges, and thebalanced-match ^4.0.2dependency is already met at 4.0.4.The top-level
brace-expansionat1.1.13is v1 and outside the affected range, so it is untouched.Notes
npm audit fixbecause the sandbox blocks the npm registry. Onlyversion/resolved/integritychanged — 9 lines, no reformat.node_modulesis not reconciled by this change; a plainnpm installwill sync the installed tree.🤖 Generated with Claude Code