feat: improve npm transitive remediation for workspaces - #264
Merged
Merged
Conversation
sonukapoor
force-pushed
the
feature/issue-250-npm-transitive-remediation
branch
from
April 30, 2026 16:57
b14dd03 to
71dd9fc
Compare
Closed
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.
This improves npm transitive remediation so the CLI can reason about logical dependency ownership more accurately, especially in workspace and hoisted-lockfile cases. It also keeps the terminal responsive after advisory detail loading by showing progress while fix validation and remediation analysis run.
The main changes are npm lock graph extraction, workspace-aware path handling, transitive parent/range resolution, and output updates for
npm update <parent>vs explicit parent upgrades. It also adds parser and remediation coverage for the workspace-specific edge cases that were previously collapsing too much package identity.Closes #250