TYPO3 Core

False positives are part of the nature of the extension scanner, as explained here:

https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/HowTo/UpdateExtensions/ExtensionScanner.html

Non-static matches are thus always marked as "weak" matches.

In this case, I'd say it's ok to keep that matcher entry (the option is to remove it).

I tend to reject the issue. I that ok with you?

Thanks Christian, that's OK for me, I can live with it. I'm just wondering whether it will be so obvious to others who use my extension ...?

Christian Kuhn wrote in #note-1:

I tend to reject the issue. I that ok with you?

Ah, I just saw that there is an option @extensionScannerIgnoreFile that I can use to prevent this (which seems legitimate in this case, since it is actually a false positive).

Cool. Thanks for quick feedback!