{"version":"2.1.319","anchor":"plugin-validate-prints-and-emits-a-content-digest","canonical_anchor":"plugin-validate-prints-and-emits-a-content-digest","heading":"Plugin validation now prints a digest of the plugin folder","tier":"use","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/plugin-validate-prints-and-emits-a-content-digest","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Plugin validation now prints a digest of the plugin folder\n\n`claude plugin validate` now prints a Digest line for the plugin folder, adds it to --json output, or says why there is none\n\n**What**\n\n`claude plugin validate` now computes a digest of the plugin folder. A digest is a short fingerprint that changes whenever any file in the folder changes. It prints it on a `Digest:` line and adds it to the output of `--json`. When it cannot make one, it prints a `No digest:` line with the reason.\n\nA digest is refused when:\n\n- The plugin's hooks module is not a code file\n\n- The hooks module names surface modules\n\nThe digest is only computed when a plugin root folder is found, and it includes the `node_modules` folder at that root.\n\n**Why**\n\nPlugin authors and plugin registries can pin the exact contents of a plugin and spot when it changes.\n\n- Area: Plugins\n- Names: `claude plugin validate`, `--json`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}