Replies: 1 comment
-
|
Hello @parrot55 As we wrote in docs - e.g. Regards, Dmitriy |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description
I launched a license scan, passing a custom config file (see trivy-custom.yaml in attachment).
I launched trivy in WSL with the following command:
trivy image --format table --scanners license --config trivy-custom.yaml --insecure --debug aquasec/trivyI also launched it in docker:
docker run -v $(pwd):/project aquasec/trivy image --format table --scanners license --config /project/trivy-custom.yaml --ignorefile /project/.trivyignore --insecure --debug aquasec/trivyThe result is the same in both cases: GPL-2.0 licenses are not classified (i.e. are unknown/UNKNOWN) when using license text like "text://GPL-2.0.*" (see trivy-custom.yaml in attachment).
The config file trivy-custom.yaml is in UTF-8. But I also tried to convert it to ANSI, with the same result.
Attachments:
trivy.log
trivy-custom.yaml
Desired Behavior
When scanning licenses with licence text, licenses are categorized as described in the documentation.
E.g.
license:
forbidden:
- "text://GPL-2.*"
classifies "GPL-2.0-only" and "GPL-2.0-or-later" as "forbidden" licenses
Actual Behavior
In the example I used, GPL-2.0-or-later and GPL-2.0-only are classified as "Non Standard" or "unknown", with a severity of "UNKNOWN" (see trivy.log in attachment)
Reproduction Steps
Target
Container Image
Scanner
License
Output Format
Table
Mode
Standalone
Debug Output
Operating System
WSL2 with Ubuntu 22.04.5 LTS
Version
Checklist
trivy clean --allBeta Was this translation helpful? Give feedback.
All reactions