You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update minimatch past GHSA-g3hv-75wg-m249 (Dependabot alert 4) #98
Josh asked for this on 2026-11-15, covering this alert only: raise minimatch to the first patched version in package-lock.json through one reviewed pull request, installing only in the builder's own working copy. If a patched minimatch cannot be reached without moving another package (a parent package pins an older major), stop and report which package and why, and do not move it. No other package moves.
Acceptance criteria
package-lock.json resolves every minimatch at or above 11.0.1, or the PR records which parent package pins an older major and the ticket stops there.
No other package version changes in package-lock.json or package.json unless the PR states why it was unavoidable.
npm audit output for minimatch is recorded in the PR, and the Dependabot alert reads fixed once the PR merges.
The repository's local checks pass.
Decision
Decided 2026-11-17: dismiss the alert as tolerable, and let the fix arrive upstream. minimatch is development scope and runs only inside the test tooling, on patterns the repository itself writes, so nothing outside the repository reaches it. The patched editorconfig 4 and glob 14 are accepted by no js-beautify release yet, and beautifier/js-beautify#2569 moves js-beautify onto minimatch 11. Once a js-beautify release carries it, a lockfile-only update clears the alert, and Dependabot opens that update itself. Rejected options: overrides forcing editorconfig 4 and glob 14 outside js-beautify's declared ranges, downgrading @vue/test-utils to 2.4.11, and leaving the alert open until the release. The alert is dismissed by the maintainer. No package moves under this ticket.
Stopped per the Scope: a patched minimatch cannot be reached without moving other packages. No branch or pull request was opened.
Why
Read against package-lock.json on main at 28c3ee0:
minimatch resolves to a single copy, 10.2.6. The vulnerable range is >= 7.0.0, < 11.0.1, so no 10.x release is patched.
Two parents pin it to 10.x:
editorconfig3.0.2 requires minimatch~10.2.4.
glob13.0.7 requires minimatch^10.2.2.
Both come from js-beautify2.0.3 (editorconfig^3.0.2, glob^13.0.6), which comes from the direct dev dependency @vue/test-utils2.5.1 (js-beautify^2.0.0).
The registry has patched parents only in new majors: editorconfig4.0.1 (minimatch~11.0.5) and glob14.0.6 (minimatch^11.0.5). js-beautify2.0.3 is its latest release and accepts neither, so reaching them would take an overrides entry in package.json that forces two parents outside their declared ranges.
npm audit
npm audit --package-lock-only against the same lockfile:
minimatch 7.0.0 - 11.0.0
Severity: moderate
minimatch has potential denial of service via globparts amplification - https://github.com/advisories/GHSA-g3hv-75wg-m249
fix available via `npm audit fix --force`
Will install @vue/test-utils@2.4.11, which is a breaking change
The only fix npm offers is a downgrade of @vue/test-utils to 2.4.11, which is another package moving.
Options for a decision
Wait for a js-beautify release that accepts editorconfig 4 and glob 14; the alert then clears with a lockfile-only update.
Add overrides for editorconfig and glob (or for minimatch directly), moving packages outside their parents' ranges.
Downgrade @vue/test-utils to 2.4.11.
Dismiss the alert as tolerable: the dependency is development scope and arrives through @vue/test-utils, a test dependency.
Activity
bpmore commentedon Nov 17, 2026
Stopped per the Scope: a patched
minimatchcannot be reached without moving other packages. No branch or pull request was opened.Why
Read against
package-lock.jsononmainat28c3ee0:minimatchresolves to a single copy,10.2.6. The vulnerable range is>= 7.0.0, < 11.0.1, so no 10.x release is patched.editorconfig3.0.2requiresminimatch~10.2.4.glob13.0.7requiresminimatch^10.2.2.js-beautify2.0.3(editorconfig^3.0.2,glob^13.0.6), which comes from the direct dev dependency@vue/test-utils2.5.1(js-beautify^2.0.0).editorconfig4.0.1(minimatch~11.0.5) andglob14.0.6(minimatch^11.0.5).js-beautify2.0.3is its latest release and accepts neither, so reaching them would take anoverridesentry inpackage.jsonthat forces two parents outside their declared ranges.npm auditnpm audit --package-lock-onlyagainst the same lockfile:The only fix npm offers is a downgrade of
@vue/test-utilsto2.4.11, which is another package moving.Options for a decision
js-beautifyrelease that acceptseditorconfig4 andglob14; the alert then clears with a lockfile-only update.overridesforeditorconfigandglob(or forminimatchdirectly), moving packages outside their parents' ranges.@vue/test-utilsto2.4.11.@vue/test-utils, a test dependency.