chore(deps): security bump — js-yaml 3.15.1 / 4.3.1 - #289
Open
sunny-se wants to merge 1 commit into
Open
Conversation
Backports the Set-based !!omap key-uniqueness fix (GHSA-5p4m-2wfm-xmqj / CVE-2026-59870): resolveYamlOmap() used O(n^2) Array.indexOf, allowing quadratic CPU on untrusted YAML. Impact scope: a11y-critical (dependency tree only — no rule or module behaviour changes). Dev-only exposure: no runtime `dependencies` declared, js-yaml comes via the build/test toolchain. Overrides-only change; lockfile regenerated with npm install --package-lock-only. npm audit reports no js-yaml findings after the bump. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
sunny-se
force-pushed
the
security/dependabot-axe-3977
branch
from
August 12, 2026 12:09
c6d7c77 to
d5b3cf8
Compare
chikara1608
approved these changes
Aug 12, 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.
Summary
package.jsonoverrides:js-yaml@33.15.0 → 3.15.1,js-yaml@44.3.0 → 4.3.1!!omapresolution; 3.15.1/4.3.1 backport theSet-based fixdependenciesdeclared — js-yaml comes via the build/test toolchain onlyVerification
npm install --package-lock-only— only js-yaml entries changed; resolves 3.15.1 / 4.3.1npm audit— no js-yaml findings after the bump