plugin validator is not suitable for a single plugin #3

Activity

1. ozsay

   changed the title [-]plugin validator is not suitable for single plugin[/-] [+]plugin validator is not suitable for a single plugin[/+] on Feb 19, 2026
2. 868Keturah commented on Apr 18, 2026

   

   868Keturah

   on Apr 18, 2026

   Last edited by 868Keturah

   More actions

   Hi @ozsay , I’d like to take this on. Happy to submit a fix.
3. deanrie commented on Oct 4, 2026

   

   deanrie

   on Oct 4, 2026

   More actions

   Hey, confirmed on current main (4621607). I moved a starter plugin's contents to the repo root exactly as the README describes (one .cursor-plugin/plugin.json, no marketplace.json) and ran node scripts/validate-template.mjs: Validation failed: Marketplace manifest is missing. So the README and the validator disagree, and the single-plugin layout the README recommends can't pass CI as shipped.

   #8 fixes it the right way: when there's no marketplace.json but there is a root plugin.json, it validates that manifest's referenced paths and component frontmatter and skips the marketplace checks. I ran it three ways: single-plugin layout passes, the default two-plugin marketplace layout still passes unchanged, and a single plugin with logo pointing at a missing file fails with the proper references missing path error, so it isn't just skipping validation. Mergeable against today's main. Flagged for the template owners.