Update build-time axios dependency to 1.16.1 to resolve security advisories#285
Merged
Conversation
…sories [#284] axios is a transitive dev/build dependency (@wordpress/scripts → jest-dev-server → wait-on → axios), not a direct dependency and not shipped in any plugin bundle. The lockfile resolved 1.13.2, below the 1.15.1 patch line for a batch of security advisories (prototype pollution, header injection, NO_PROXY bypass, CRLF injection, SSRF). wait-on already permits ^1.12.1, so only package-lock.json changes — no overrides needed. npm audit now reports no axios advisories and the production build still succeeds. 🐦⬛ Generated with Claude Code, orchestrated by Crow Co-Authored-By: Claude <noreply@anthropic.com> Crow-Session: 813E287D-548F-42EA-8624-A08C354D2A6C
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.
Closes #284
What
Bumps the transitive axios dependency from 1.13.2 → 1.16.1 in
package-lock.json.Why
axios is not a direct dependency — it's pulled in only by the dev/build toolchain (
@wordpress/scripts → jest-dev-server → wait-on → axios) and does not appear in any shipped bundle (assets/js/dist/), so the vulnerable code never reaches WordPress users. The lockfile resolved 1.13.2, which is below the 1.15.1 patch line for a batch of advisories (prototype pollution, header injection, NO_PROXY bypass, CRLF injection, SSRF, etc.). This clearsnpm auditand keeps the dev toolchain current.wait-onalready declaresaxios: "^1.12.1", which permits 1.16.1, so nooverridesblock was needed — onlypackage-lock.jsonchanged (package.jsonis untouched, axios stays transitive).Verification
grep -A1 '"node_modules/axios"' package-lock.json→"version": "1.16.1"npm audit→ no axios advisoriesnpm run build→ compiled successfully🤖 Generated with Claude Code