{"version":"2.1.323","anchor":"marketplace-plugin-content-verified-against-commit-proof","canonical_anchor":"marketplace-plugin-content-verified-against-commit-proof","heading":"A check compares installed marketplace plugin files with their source","tier":"internal","area":"Plugins","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/marketplace-plugin-content-verified-against-commit-proof","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### A check compares installed marketplace plugin files with their source\n\nClaude Code can now check an installed plugin's folder against a stored proof of the git commit it came from\n\n**Unclear.** It is not clear when Claude Code runs this check or what happens when it reports a difference.\n\n**What**\n\nClaude Code has a new check that compares an installed plugin's folder with the git commit (a saved version of the plugin's code) it should match, using a stored proof. The check reports one of these results:\n\n- absent\n\n- unreadable\n\n- no proof\n\n- differs\n\n- proved\n\nMessages include cases where a file is not in the commit, or where the proof belongs to another commit.\n\n**Why**\n\nThis looks like a way to confirm that installed plugin files have not drifted from the version they were installed from.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}