{"version":"2.1.280","anchor":"git-integrity-check-surfaces-tampered-object-detection","canonical_anchor":"git-integrity-check-surfaces-tampered-object-detection","heading":"Git integrity check surfaces tampered object detection","tier":"notice","area":"Git Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/git-integrity-check-surfaces-tampered-object-detection","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Git integrity check surfaces tampered object detection\n\nGit integrity checks now detect and report tampered objects with a count\n\n**What**\n\nWhen Claude Code checks the health of a git repository, it can now recognize a specific kind of failure: objects that appear to have been tampered with. This is reported as a distinct `tampered_objects` cause, along with a count of how many objects were flagged, rather than being lumped in with generic git errors.\n\n**Why**\n\nSeparating this out makes it clearer, when a repository check fails, whether the problem is ordinary git trouble or something more concerning like altered objects, and gives a concrete count to act on.\n\n- Area: Git Integration\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}