fix: remove npm-check devDependency to resolve execa vulnerability#86
Open
tiaanduplessis wants to merge 2 commits intomasterfrom
Open
fix: remove npm-check devDependency to resolve execa vulnerability#86tiaanduplessis wants to merge 2 commits intomasterfrom
tiaanduplessis wants to merge 2 commits intomasterfrom
Conversation
…bility npm-check pulled in execa@0.2.2 which has a critical security finding. Since npm-check is only used as a convenience tool, switch to npx invocation to avoid carrying the vulnerable transitive dependency. Closes #85 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <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
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.
Removes npm-check from devDependencies to eliminate the critical security vulnerability in its transitive execa@0.2.2 dependency. The check script now uses npx to invoke npm-check on-demand, avoiding the need to maintain the vulnerable package in the lockfile.
Closes #85