chore: npm audit fix — update js-yaml 4.1.1 → 4.2.0#492
Merged
Conversation
Copilot
AI
changed the title
[WIP] Run npm audit fix without overrides or force flags
chore: npm audit fix — update js-yaml 4.1.1 → 4.2.0
Jun 17, 2026
rzhao271
approved these changes
Jun 17, 2026
benibenj
approved these changes
Jun 17, 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
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 a moderate-severity DoS vulnerability (GHSA-h67p-54hq-rp68) in
js-yamlcaused by quadratic-complexity behavior in merge key handling via repeated aliases.Changes
package-lock.json:js-yamlbumped4.1.1→4.2.0(transitive dev dependency via eslint toolchain)Notes
--forceflag required; standardnpm audit fixresolved all vulnerabilities--forceto fixpackage.jsonunchanged —js-yamlis not a direct dependencyOriginal prompt
Created from VS Code.