Skip to content

fix(cli): unexpected ordering in trivy args records the wrong command #9259

@owenrumney

Description

@owenrumney

If the user calls Trivy in a way that isn't "expected", such as trivy -d --scanners vuln image nginx, this is perfectly valid execution but the incorrect command is picked up.

Update the creation of the versionChecker to use the targetKind rather than infering the target from the first OS argument

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions