fix(deps): bump js-yaml and nanoid to resolve CVE-2026-59870 and GHSA-2v37-7h3g-55p8 - #14
Merged
Merged
Conversation
…-2v37-7h3g-55p8 js-yaml 3.15.0 -> 3.15.1 and the two nested 4.3.0 copies -> 4.3.1 (quadratic CPU consumption in !!omap resolution, CVE-2026-59870 / GHSA-5p4m-2wfm-xmqj); nanoid 3.3.16 -> 3.3.18 (custom generators can loop indefinitely when size is zero, GHSA-2v37-7h3g-55p8). All bumps fit the existing semver ranges, so this is lockfile-only in both package-lock.json and yarn.lock, no package.json changes. Verified with `yarn install --frozen-lockfile` and `yarn build`. npm audit drops from 10 to 8 high findings; the remaining 8 are all the unfixable image-size chain tracked in REV-98 (metro 0.84.5 removed image-size on 2026-08-19, pending an Expo repin). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ashirman
approved these changes
Aug 20, 2026
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
2 participants
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.
Summary
!!omapresolution).All new versions fit the existing semver ranges (
^3.13.1,^4.1.0/^4.1.1,^3.3.16), so this is a lockfile-only change in bothpackage-lock.jsonandyarn.lock— nopackage.jsonedits needed.Not included (no fix available)
The remaining 8
npm audithigh findings are all one chain rooted inimage-size(no fixed npm release exists; tracked in REV-98). metro removedimage-sizein 0.84.5 / 0.83.8 on 2026-08-19, but@expo/metro@56.0.0still pins metro to exactly 0.84.4, so that fix lands as a follow-up lockfile bump once Expo repins. A daily routine now watches for that release.Verification
yarn install --frozen-lockfile— passesyarn build— passesnpm audit— high findings drop from 10 to 8; js-yaml and nanoid no longer reported🤖 Generated with Claude Code