Replies: 5 comments
-
Thanks @bmiro for opening the issue. |
Beta Was this translation helpful? Give feedback.
-
It would be nice to be able to ignore by |
Beta Was this translation helpful? Give feedback.
-
This issue is stale because it has been labeled with inactivity. |
Beta Was this translation helpful? Give feedback.
-
/remove-lifecycle stale |
Beta Was this translation helpful? Give feedback.
-
This issue is stale because it has been labeled with inactivity. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I was trying to filter the vulnerabilities by Type (as in the
json
format) i.e. to not report vulnerabilities found in Gemfiles or yarn if the project is a PHP (with composer).I'm not sure if it can be done, for now I've tried the following:
The option
--vuln-type
but it only refers toos
orlibrary
notcomposer
,yarn
. This option does not refer to the sameType
as thejson
output. So is not useful for me. Maybe would be nice to have the something--ignore-vuln-target-type xxxx,yyyy
or--vuln-target-type xxxx,yyyy
?Also seen the option
--skip-files
or--skip-dir
but we use trivy for generic scans on repos and we do not know the full path to files to skip. It would work with wildcards like--skip-files '*/yarn.lock' --skip-files '*/Gemfile'
but they not seem to be supported.Finally there is the option to use
--ignore-policy
with a Rego file. But theinput
in rego does not seem have theType
nor theTarget
of the vulnerability as type is on the parent in the json:I've tried this regofile without success:
I'm missing something? There is any way to filter by
Target
(with wildcards) orType
?If not I think I can try to do a PR with the changes but I'm not sure with is the best option of the following:
Target
/Type
to the input at the rego fileI would like to give a hand if you thing this is appropriate : )
Many thanks for the effort developing the software and attending those questions : )
Beta Was this translation helpful? Give feedback.
All reactions