Repository navigation
fix(deps): patch axios, moment and brace-expansion advisories - #215
Open
TartanLeGrand wants to merge 1 commit into
Open
TartanLeGrand wants to merge 1 commit into
TartanLeGrand wants to merge 1 commit into
Conversation
npm audit reported three advisories on main: axios prototype pollution gadgets (high, direct dependency), brace-expansion quadratic expansion (high) and moment locale path traversal (moderate). Lockfile only: axios 1.18.1 to 1.20.0, moment 2.30.1 to 2.31.0, brace-expansion 5.0.9 to 5.0.12.
This branch has not been deployed
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.
What
npm auditonmainreports three advisories published since #206:axios(direct)brace-expansion(transitive)moment(transitive, viamoment-timezone)Lockfile only, every bump stays inside the ranges already declared in
package.json.axios 1.20 notes
The release lists one "breaking change": new status names
ContentTooLarge(413) andUnprocessableContent(422), with the old names kept as aliases. One behaviour fix worth knowing: an XHR canceled by a page navigation now rejects withECONNABORTEDinstead of resolving with status 0. The web code uses neither the status names nor a status 0 check.Checks
npm audit: 0 vulnerabilities (was 3).npm run buildandnpm run build:static: green.tsc --noEmit: 122 errors andeslint .: 78 errors / 165 warnings, both identical tomain.Note
#201 regenerates the same lockfile; whichever merges second needs a rebase.