Your Exposed .git Directory Is a Source-Code Fire Sale: What Attackers Actually Pull From It
Most teams treat an exposed /.git/ directory as a cosmetic misconfiguration. It is worse: with the config, index, HEAD and reflog readable, an attacker can enumerate your tracked files, your remotes, your commit timeline — and reconstruct the repository byte-for-byte offline. Here is what each file actually leaks, and how to prove (not guess) whether yours is exposed.