Bump nanoid to 3.3.18 (GHSA follow-up) - #266
Merged
Merged
Conversation
Same advisory family as the 3.3.17 bump (customAlphabet/customRandom infinite loop on size=0); the upstream 3.3.17 patch was incomplete and 3.3.18 supersedes it. Still a transitive build-time dependency (vite -> postcss -> nanoid), still not reachable with attacker input here. Lockfile-only: postcss's ^3.3.16 constraint permits it, so only nanoid's version/resolved/integrity move. 3.3.18 is the newest release in the 3.x line postcss is locked to.
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.
Resolves the follow-up Dependabot alert #77: the upstream 3.3.17 patch for the
customAlphabet/customRandomsize=0 infinite loop was incomplete, and 3.3.18 supersedes it.Same posture as #261: transitive build-time dependency (
vite->postcss->nanoid), not shipped to browsers, no attacker-controlled size reaches those functions, so real exposure is negligible - but the patch is free. Lockfile-only bump within postcss's^3.3.16constraint; only nanoid'sversion/resolved/integritylines move andnpm cistays in sync.3.3.18 is the newest release in the 3.x line postcss is pinned to, so this is as far forward as this dependency can roll until upstream cuts another backport.