Ignored Locations

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.

Match Types

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.

Prefix

Specify a Path prefix that should be ignored. Every directory or file that begins with Path will be ignored. The value is case insensitive.

Example: /vendor/

Partial

Specify a keyword that can occur anywhere in the Path.
If you would like to match a directory, make sure to add slashes to avoid partial matches on file names. The value is case insensitive.

Example: /tests/

Regex

Specify a regular expression in the Path. The regex will be applied to the full path (lower case).
Make sure to escape slashes and dots with back-slashes. The value is case sensitive, only expect lower case characters.

Example: .*\/vendor\/.*\/tests

Exclude Types

There are five different types of ignores that can be influenced by the filter.

AnalysisAll applicable folders are excluded from the whole analysis. No sinks, sources and other operations will be detected from them.
Code QualityFunctionality of these folders is included in the analysis, but no possible code quality issues in these are included in the result.
SecurityFunctionality of these folders is included in the analysis, but no possible secuirty issues in these are included in the result.
MisconfigurationFunctionality of these folders is included in the analysis, but no possible misconfigurations in these are included in the result.
PatchFunctionality of these folders is included in the analysis, but no possible patches in these are included in the result.