Skip to content

Fix high-severity npm audit failures - #536

Merged
srtfisher merged 3 commits into
developfrom
fix/npm-audit-picomatch
Apr 21, 2026
Merged

Fix high-severity npm audit failures#536
srtfisher merged 3 commits into
developfrom
fix/npm-audit-picomatch

Conversation

@srtfisher

Copy link
Copy Markdown
Member

Summary

  • Runs npm audit fix --package-lock-only to bump the transitive picomatch dep past GHSA-3v7f-55p6-f55p and GHSA-c2c7-rcm5-vvqj, which were breaking CI.
  • Remaining advisories are moderate and fall below the audit threshold.

Test plan

  • composer phpcs
  • composer phpstan
  • composer rector (dry-run)
  • npm run check-types
  • npm run eslint
  • npm run stylelint

Updates package-lock.json via `npm audit fix --package-lock-only` to
resolve the high-severity picomatch advisories (GHSA-3v7f-55p6-f55p,
GHSA-c2c7-rcm5-vvqj) that were breaking CI. Remaining moderate
advisories are under the audit threshold.
@srtfisher
srtfisher merged commit df8f2e3 into develop Apr 21, 2026
5 checks passed
@srtfisher
srtfisher deleted the fix/npm-audit-picomatch branch April 21, 2026 17:43
srtfisher added a commit that referenced this pull request Jun 15, 2026
The CI Node Tests step runs `npm audit --audit-level=high --omit=dev`,
which failed on fast-uri <=3.1.1 (path traversal GHSA-q3j6-qgpj-74h6 and
host confusion GHSA-v39h-62p7-jpjc), pulled in transitively via ajv and
the @wordpress/* packages.

Add an npm override pinning fast-uri to ^3.1.2 (the patched 3.x release,
compatible with ajv's ^3.0.1 constraint). Resolves the only high-severity
advisory; the remaining moderates are tolerated by --audit-level=high,
consistent with #536.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant