Package Mask Configurations
Package Masks allow users to configure the naming of their own internal packages (if they have any). This configuration does two things. First, when these packages are encountered in a scan they will be marked as Internal and will not show as Unknown Package Issues, as would otherwise be the case. Second, and probably more importantly, setting package masks ensures that SOOS protects you against Dependency Substitution Issues.
Package masks support wildcards, for cases where you want to specify the prefix or suffix and not list every package name as well as ensure that new packages will automatically be matched.
To link a particular internal package to a specific project, make sure to define the package mask on the corresponding project's configuration and be as specific as possible. You can still set a global wildcard to ensure that new packages are caught as well (see Configuration Inheritance for more details on configuration inheritance).
