fix: bump js-yaml to 3.15.2 to resolve audit advisory - #67
Merged
Merged
Conversation
…v3hh The Security Scan step in CI (pnpm audit --audit-level moderate) has been failing on every open pull request because of a high-severity advisory in js-yaml, pulled in transitively through gray-matter. The lockfile pinned js-yaml at 3.15.1, which falls inside the vulnerable range (>=3.0.0 <3.15.2). Running pnpm update js-yaml --depth Infinity re-resolves it to 3.15.2, which still satisfies gray-matter's existing ^3.13.1 dependency range. This change is lockfile-only: no package.json edit and no pnpm override were needed. Re-resolution also picked up two incidental, in-range bumps: nanoid moved from 3.3.18 to 3.3.19, and a second copy of rollup 4.63.4 was added as a transitive dependency under vitest (the direct rollup 4.63.1 dependency is unchanged). Verified pnpm audit --audit-level moderate now reports no known vulnerabilities, the full test suite (282 tests) passes, and pnpm build completes cleanly.
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.
Summary
pnpm audit --audit-level moderate) has been failing on every open pull request because of a high-severity advisory, GHSA-2883-xcg3-v3hh, injs-yaml. The vulnerable range is>=3.0.0 <3.15.2, and the lockfile pinnedjs-yaml@3.15.1, pulled in transitively throughgray-matter.pnpm update js-yaml --depth Infinity, which re-resolvesjs-yamlto3.15.2. That version still satisfiesgray-matter's existing^3.13.1dependency range, so this change is lockfile-only: nopackage.jsonedit and no pnpm override were needed.Changes
Dependencies
js-yamlto3.15.2to resolve GHSA-2883-xcg3-v3hh. Re-resolution also picked up two incidental, in-range bumps:nanoidmoved from3.3.18to3.3.19, and a second copy ofrollup@4.63.4was added as a transitive dependency under vitest (the directrollup@4.63.1dependency is unchanged).Test plan
pnpm audit --audit-level moderatereports "No known vulnerabilities found"pnpm buildcompletes cleanlyNotes
This unblocks the open Dependabot PRs #64, #65, and #66, which all currently fail on this same Security Scan gate and should go green once they rebase on
main.