Plugin Submission Requirements
Last updated: July 14, 2026
Every release submitted to Creator Bazaar goes through automated validation and security analysis before it can be approved. Submissions that fail these requirements are rejected or quarantined, and repeated abuse can lead to publisher suspension.
1. Packaging and manifest
- The bundle must be a well-formed plugin archive with a valid manifest (name, version, entry point) that matches the listing it is submitted under.
- Versions must be unique per plugin and follow semantic versioning.
- The bundle must stay within the published size limits for plugin archives.
2. Security
- Bundles are scanned for malware; any detection quarantines the release automatically.
- Releases with critical or high severity security findings are blocked from approval. Resolve the findings and submit a new release.
- Do not include embedded secrets (API keys, tokens, credentials) or code that exfiltrates user data.
- Heavily obfuscated code that prevents analysis may be rejected; minified production builds are acceptable.
3. Behavior and content
- The plugin must do what its listing says: names, descriptions, and screenshots must not be misleading.
- Network access, data collection, and third-party services the plugin uses should be disclosed in the description or documentation.
- Content must be lawful and must not infringe third-party intellectual property, privacy, or publicity rights.
4. Listing quality
- Provide a clear display name, description, and category.
- An icon, screenshots, documentation, and support links are strongly recommended — they appear in the plugin’s Trust Center and improve install confidence.
5. Review outcomes
Approved releases become installable immediately after you publish them. Rejected or blocked releases include the reason in your publisher dashboard, and release status changes are also sent by email. Moderators may re-review and unpublish previously approved content that later turns out to violate these requirements or the Terms of Service.