Dev Tools · 17h ago
Git History Can Be Faked: Why Devs Need External Proof
Git commit dates and authorship can be rewritten using commands like git commit --date or rebase, making the log unreliable for legal disputes. Force-pushes can erase history entirely, and even signed commits lack independent timestamps. To prove priority, developers should use RFC 3161 Time-Stamping Authorities for cryptographically verified, third-party timestamps.
Meridian48 take
This is a practical warning for startups and freelancers, but the article overstates the risk for most teams — branch protection and signed commits already cover many scenarios.
git-securitycode-authorship