chore(security): patch 2 Dependabot alerts - #1839
Merged
Merged
Conversation
Fixes js-yaml transitive vulnerabilities (GHSA CVE-2026-59870) by pinning 4.x consumers to ^4.3.1 and 3.x consumers to ^3.15.1 via scoped resolutions. Also removes 5 resolutions that are now redundant (natural resolution already satisfies the pin). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
Coverage Impact This PR will not change total coverage. 🚦 See full report on Qlty Cloud »🛟 Help
|
Tonours
approved these changes
Aug 20, 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
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.
Summary
2 fixed, 2 ignored, 0 deferred, 7 resolutions added, 5 resolutions removed, 0 could-not-auto-fix. | label: 🔒 security applied
Fixed
lerna,cosmiconfig,eslint,@eslint/eslintrc,@semrel-extra/topo) pinningjs-yamlto^4.3.1@oclif/core,@istanbuljs/load-nyc-config) pinningjs-yamlto^3.15.1Ignored
first_patched_versionisnullfor the JXL/HEIF infinite-loop advisory.first_patched_versionisnullfor the ICNS infinite-loop advisory.Deferred
None. All open alerts were >=7 days old on 2026-08-20 (created 2026-08-07 and 2026-08-10).
Resolutions added
js-yaml^4.3.1underlerna,cosmiconfig,eslint,@eslint/eslintrc,@semrel-extra/topojs-yaml@^4.1.0— no ancestor bump would raise the resolved sub-dep to 4.3.1. The existing**/lerna/js-yaml: ^4.2.0needed updating too.js-yaml^3.15.1under@oclif/core(nested inforest-cli) and@istanbuljs/load-nyc-config(nested under Jest's instrumentation chain)forest-cli/@oclif/core(touches API surface) and re-tagging the Jest instrumentation chain (owned upstream). Neither is worth the blast radius for a patch fix.^3.13.1/^3.14.1, both compatible with^3.15.1.Resolutions removed
**/socks/ip-address: ^10.3.1ip-address@10.5.0satisfies^10.3.1(socks' parent chain now resolves 10.5.0 without help).**/ajv/fast-uri: ^3.1.5fast-uri@3.1.5still satisfies^3.1.5(top-levelfast-urihas moved to 3.1.5).**/@modelcontextprotocol/sdk/hono: ^4.12.34hono@4.13.3satisfies^4.12.34.@modelcontextprotocol/sdk: ^1.30.0@modelcontextprotocol/sdk@1.30.0satisfies^1.30.0.**/@hono/node-server: ^2.0.5@hono/node-server@2.1.1satisfies^2.0.5.Could not auto-fix
None.
Risks
!!omapquadratic-CPU fix (CVE-2026-59870). No API changes. No behavior change beyond the patched vuln.!!omapfix backport to the 3.x line. No API changes.js-yamlfrom within the^4.1.0bound its own manifest declares. Compatibility verified viayarn install --ignore-scripts(installs cleanly).Manual testing
Covered by CI. The vulnerable API path (
!!omapYAML tag resolution) is only exercised by the linked parent tools during their normal load — full CI exercises the toolchain end-to-end.Validation
✅ CI green (Actions + commit statuses; app-based checks not monitored)