feat(scanner) add dev flag in library#2405
Merged
Conversation
MaineK00n
reviewed
Feb 4, 2026
…o add_dev_flag_in_library
…ibsCves with configurable lockfile paths
MaineK00n
reviewed
Feb 5, 2026
MaineK00n
reviewed
Feb 5, 2026
…o add_dev_flag_in_library
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.
Summary
Move dev dependency detection control from
AnalyzeLibrary(scanner) toDetectLibsCves(detector).Changes
DetectDevLockfilePathsfield toTrivyOptsDevflag)DetectLibsCvesskips vulnerability detection for dev dependencies unless the lockfile path is specified inDetectDevLockfilePathsincludeDevDependenciesparameter fromAnalyzeLibraryUsage
Only the specified lockfiles will detect vulnerabilities in dev dependencies. If not specified, dev dependencies are skipped (default behavior).