Repository navigation
chore(deps): bump brace-expansion within range - #30
Merged
Merged
Conversation
Fixes GHSA-6j4f-fj2g-mc7p, GHSA-qhr7-859c-m2p7 and GHSA-q2hr-2g5m-vwhr in the eslint/minimatch tooling chain. Dev-only; lockfile only. Co-Authored-By: Claude Opus 5.5 <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
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.
Problem
npm auditreports 20 dev-only advisories (2 critical, 13 high). The published package has no dependencies, andnpm audit --omit=devis clean, so none reach n8n users. Dependabot shows only 3 of them (axios, stream-json, uuid).Solution
Lockfile-only: brace-expansion 1.1.18 → 1.1.21 and 5.0.9 → 5.0.12, within existing ranges. This fixes GHSA-6j4f-fj2g-mc7p (high), GHSA-qhr7-859c-m2p7 (high) and GHSA-q2hr-2g5m-vwhr. Both versions were published at least 7 days ago by the same publisher (
juliangruber), and their integrity hashes match the registry.The rest is blocked upstream for now:
n8n-workflowpins it exactly. The first release pinning 1.20.0 is 2.43.4, published 2026-10-15. Bumpn8n-workflowonce it is at least 7 days old.@n8n/node-cli(through 0.53.1) and@n8n/backend-network.@n8n/node-cli's AI-SDK chain.overrideswould fix most of these, butn8n-node lintrejects that field in community packages (@n8n/community-nodes/no-overrides-field).Note: #29 adds
npm audit --audit-level=hightovalidate. Until the upstream pins move, that gate fails on the axios and handlebars highs.Testing
CI green on Node 22.22 and 24. Locally,
npm ciandnpm run validatepass: prettier, lint, typecheck, 21/21 tests,npm audit --omit=dev, check-package.🤖 Generated with Claude Code