Repository navigation
fix: remove audited vulnerable transitive dependencies - #2
Merged
Merged
Conversation
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.
The Jest tooling dependency path js-yaml → argparse 1.x → sprintf-js is affected by GHSA-hp3w-g68c-fv3c. Resolve argparse to 2.0.1 within js-yaml, removing sprintf-js while retaining legacy CLI compatibility. Other dependency versions remain locked.
Regression checks cover the installed resolution, NYC YAML arrays, booleans and field normalization, malformed YAML rejection and the legacy YAML CLI. The CLI retains functionality and emits argparse deprecation warnings.
Clean npm ci, npm audit (zero findings), actual TypeScript checks, existing unit tests, build and package checks where applicable passed. Workflows, thresholds and security settings are preserved.