{"version":"2.1.251","anchor":"more-checks-before-a-plugin-s-commands-are-trusted","canonical_anchor":"more-checks-before-a-plugin-s-commands-are-trusted","heading":"More checks before a plugin's commands are trusted","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/more-checks-before-a-plugin-s-commands-are-trusted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### More checks before a plugin's commands are trusted\n\nPlugin commands face many more safety checks before they are trusted.\n\n**What**\n\nPlugin command sources go through a much larger set of named validation failures now, covering suspicious symlinks, network paths, entries that resolve somewhere other than where they claim, directories that are too large or hold too many files, and mismatches with the consent you previously gave.\n\n**Details**\n\n- Runs on the normal path for loading a plugin's commands, with no flag involved.\n\n**Evidence**\n\n`plugin command source relink target resolves to a network path`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}