Hello - thanks for your reply. We’re looking into this issue with folder names causing false positives when publishers are using . in naming conventions. I’m hoping we can change the rules to ignore folder/path names when checking for extensions. But for now, yes, avoiding . in names should solve the issue.