@User, @User @User: My best guess is that is related to an "incident" that happened some time ago where apparently some proprietary information was committed by error . (I have received a mail on this topic because I cloned the repo at the time the incident happened)