Not always the whole application code should be included in the analysis process or you don't want to see results from third-party libraries. To customize the analysis and the report, whole paths or single folders can be ignored.
Paths can be specified as either prefix, partial, or regex. The settings window shows an example with highlighting as you type of the path that will be ignored.
Specify a path prefix that should be ignored. Every directory or file that begins with this path will be ignored. The value is case insensitive.
Specify a keyword that can occur anywhere in the path.
Specify a regular expression for the path. The regex will be applied to the full path (lower case).
There are five different types of ignores that can be influenced by the filter.
|Analysis||All applicable folders are excluded from the whole analysis. No sinks, sources, and other operations will be detected in them.|
|Code Quality||Functionality of these folders is included in the analysis, but no code quality issues in these are included in the result.|
|Security||Functionality of these folders is included in the analysis, but no possible security issues in these are included in the result.|
|Misconfiguration||Functionality of these folders is included in the analysis, but no possible misconfigurations in these are included in the result.|
|Patch||Functionality of these folders is included in the analysis, but no possible patches in these are included in the result.|