Ignore js-yaml merge advisory for real - #1071
Merged
Merged
Conversation
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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.
Two advisories landed on 2026-07-27 and generated yet another seven Snyk fix PRs (#1064 through #1070).
SNYK-JS-JSYAML-18313070 (inefficient algorithmic complexity in readFlowCollection, CVSS 8.7) is fixed only in js-yaml 5.2.2. There is no backport in the 4.x line, so the lockfile re-resolution used in #1056 cannot reach it, and js-yaml 5.0.0 is a breaking rewrite (flat named exports, YAML 1.2 number parsing instead of 1.1, reorganized schema exports) that deserves a deliberate migration rather than an automated bump. This PR adds a
.snykpolicy ignoring the advisory with a 90-day expiry (2026-10-25). Snyk's GitHub integration reads.snykper manifest directory rather than from the repo root, so the file is duplicated into each directory it scans as its own project, plus one at the root so localsnyk testruns agree with CI.Exposure is not very serious in the meantime. The affected parse path handles front matter and config from documents the user has already opened locally, not untrusted network input, so the worst case is a self-inflicted editor hang.