Repository navigation
fix(deps): update follow-redirects to 1.16.1 for high-severity advisories - #6
Merged
Merged
Conversation
…ries Lockfile only. follow-redirects 1.16.0 (via axios) is affected by GHSA-q3jh-wrc6-jgq8 and GHSA-8r9p-f939-6h3c. No axios release requires a fixed follow-redirects yet (axios 1.20.0, the latest, asks for ^1.16.0), so the dependencies range cannot exclude it. Also updates dev-only brace-expansion 1.1.13 -> 1.1.21 and js-yaml 4.1.1 -> 4.3.2 (via eslint 8).
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.
Advisories
axios@1.20.0 > follow-redirectsaxios@1.20.0 > follow-redirectseslint > minimatch > brace-expansioneslint > js-yaml,eslint > @eslint/eslintrc > js-yamlHow
Lockfile only;
package.jsonis unchanged.follow-redirects1.16.0 -> 1.16.1 (published 2026-10-01). 1.16.2 is one day old, so it was not picked.brace-expansion1.1.13 -> 1.1.21,js-yaml4.1.1 -> 4.3.2, both within eslint 8's existing ranges. No major upgrades.overrides.Gap for SDK users
Consumers ignore this lockfile, so what they install depends on the
axiosrange independencies. The plan was to raise theaxiosfloor to a release that requires a fixedfollow-redirects, but none exists yet: axios 1.20.0 (latest, 2026-08-26) asks forfollow-redirects ^1.16.0, which still allows 1.16.0.keymintare already safe, because^1.16.0resolves to the newest 1.16.x.npm update follow-redirects. The CHANGELOG entry says this.follow-redirects >=1.16.1and that release is two weeks old, raise ouraxiosfloor to it.Results
npm audit --omit=dev: 0 vulnerabilities (was 1 high)npm audit: 0 vulnerabilities (was 3 high)npm run lint,tsc --noEmit,npm run build: passnpm test: 49/49 passNo version bump, tag or publish.