deps: bump js-yaml to 4.3.2 to close a new HIGH alert - #141
Conversation
GHSA-2883-xcg3-v3hh (CVSS 7.5): maxTotalMergeKeys does not limit CPU use for empty merge sources. Follow-up to the 4.3.1 advisory fixed last month. js-yaml is a transitive dev dependency and its only dependent declares ^4.3.0, so 4.3.2 satisfies it without an override. One hoisted copy. Closes alert #177.
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
A new HIGH alert (#177, GHSA-2883-xcg3-v3hh, CVSS 7.5) landed on
mainminutes after #140 merged:maxTotalMergeKeysdoes not limit CPU use for empty merge sources. It is the follow-up to the js-yaml advisory fixed last month, which took us to 4.3.1. The fix is 4.3.2.Change
Lockfile only, 3 lines. js-yaml is a transitive dev dependency and its only dependent declares
js-yaml: ^4.3.0, so 4.3.2 satisfies it with nooverridesentry. There is a single hoisted copy in the tree, now at 4.3.2.Verification
vitest run: 1078 passed (49 files)tsc --noEmit: cleannpm run lintstill fails the same way it does onmain(TypeError: Converting circular structure to JSONinside ESLint's own config loader). Pre-existing and unrelated, same as on #140.