{"version":"2.1.233","anchor":"plugin-and-marketplace-validation-no-longer-follows-symlinks","canonical_anchor":"plugin-and-marketplace-validation-no-longer-follows-symlinks","heading":"Plugin and marketplace validation no longer follows symlinks","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/plugin-and-marketplace-validation-no-longer-follows-symlinks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Plugin and marketplace validation no longer follows symlinks\n\nPlugin validation stops following symlinks and tells you what it skipped, so passing means less than before.\n\n**What**\n\nValidation now refuses to follow symlinks and reports what it skipped, so a passing validation no longer implies the real target was checked. Install behaviour is unchanged and still dereferences them.\n\n**Details**\n\n- A local marketplace source that is a symlink, or reached through one, produces a warning saying install still dereferences it and that the real path should be validated separately.\n- Files that are symlinks, are not regular files, or exceed a size cap are reported as unvalidated rather than passing.\n- A path component that exists but is not a directory now yields an ENOTDIR error; the shared checker classifies each component as ok, absent, not-a-directory or refused.\n- Skill, agent and command discovery now count the symlinked entries they skipped.\n\n**Evidence**\n\n`validation never follows one. Install dereferences symlinks that stay inside the marketplace, so this entry still loads. Validate the real path separately.`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}