docs: explain remediation target selection#267
Merged
sonukapoor merged 1 commit intomainfrom Apr 30, 2026
Merged
Conversation
sonukapoor
force-pushed
the
feature/issue-262-upgrade-target-docs
branch
from
1251ef7 to
e9451b6
Compare
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.
Adds a focused remediation strategy guide that explains how CVE Lite CLI chooses direct upgrade targets, parent updates, and parent upgrades for transitive findings.
This also makes parent-aware transitive remediation more visible in the README comparison, the comparison guide, the docs homepage, and the general how-it-works page. The goal is to explain why the CLI recommends updating the parent package instead of installing a transitive child directly, especially for npm workspace and hoisted dependency cases.
Docs-only change; build and test were not run.
Closes #262