chore: Security enhancements - #407
Merged
Merged
Conversation
Bump js-yaml 4.3.0 to 4.3.1 (eslint/mocha) and 3.15.0 to 3.15.1 (nyc's load-nyc-config) to resolve the quadratic CPU consumption advisory in !!omap resolution (CVE-2026-59870). Dev-only dependency, lockfile-only change.
chrisdp
marked this pull request as ready for review
August 7, 2026 18:56
chrisdp
enabled auto-merge (squash)
August 7, 2026 18:56
TwitchBronBron
approved these changes
Aug 7, 2026
TwitchBronBron
disabled auto-merge
August 7, 2026 18:56
TwitchBronBron
enabled auto-merge (squash)
August 7, 2026 18:56
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 the js-yaml high severity advisory (quadratic CPU consumption in
!!omapresolution, CVE-2026-59870) reported by npm audit.Bumps js-yaml 4.3.0 to 4.3.1 (under eslint/mocha) and 3.15.0 to 3.15.1 (under nyc's load-nyc-config) via
npm audit fix. js-yaml only appears in the dev dependency tree, so this is a lockfile-only change with no consumer impact.npm auditnow reports 0 vulnerabilities and the full test suite passes.