Raise the js-yaml floor past the omap CPU advisory - #102
Merged
Conversation
GHSA-5p4m-2wfm-xmqj (CVE-2026-59870) — quadratic CPU consumption resolving `!!omap`, fixed in 4.3.1. Published after the last green DoD, so the Trivy filesystem scan started blocking every run on main, including the one gating the deploy of #98. Only console depends on js-yaml, and the range already admitted the fix; this raises the floor so the lockfile can't drift back. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
dependency-scan(Trivy fs, HIGH/CRITICAL, fixable-only) started failing on every run overnight:The advisory was published after the last green DoD, so this is not a regression from any recent change — it blocks the gate for everything, including the deploy of #98 (per-application resources), which is why
coach-mcp.fps4.nlstill can't be authorised against.Only
consoledepends on js-yaml and its range (^4.3.0) already admitted the fix, so this is a lockfile refresh plus a floor bump so the lock can't drift back.Verified on the re-run of #98's DoD that all four build/test jobs (
service,sdk,react,console) are green —dependency-scanwas the sole red.🤖 Generated with Claude Code