Publishing to the Marketplace

The OmniLux marketplace hosts curated, reviewed plugins that users can install with a single command.

Submission requirements

Before submitting, ensure your plugin:

1. Has a valid manifest — passes omnilux plugin validate ./your-plugin
2. Declares minimal permissions — only request what you actually need
3. Includes documentation — a README explaining what the plugin does, how to configure it, and any requirements
4. Has a license — must be open source (MIT, Apache-2.0, GPL-3.0, etc.)
5. Has tests — at least basic tests for your adapter implementations
6. Works with the latest OmniLux version — test against the current release

Legal requirements

Marketplace plugins must not:

• Facilitate piracy or circumvent DRM
• Include malware, tracking, or data exfiltration
• Violate third-party terms of service
• Contain obfuscated code

Gray-area functionality (indexer scrapers for piracy sites, etc.) is not allowed in the marketplace. Community plugins can provide this functionality, but they are not hosted or endorsed by OmniLux. See Community Plugins.

Submission process

1. Push your plugin to a public GitHub repository
2. Open a submission issue on the OmniLux marketplace repository using the plugin submission template
3. Automated review — CI runs validation, builds the plugin, and checks for common issues
4. Manual review — a OmniLux maintainer reviews the code for quality, security, and compliance
5. Approval — once approved, the plugin is listed in the marketplace

Versioning and updates

• Use SemVer for versioning
• Publish updates by pushing a new tag to your repository and opening an update request
• Breaking changes require a major version bump
• The marketplace tracks your GitHub repository — users are notified of available updates

Review timeline

• Automated checks: immediate
• Manual review: typically 3–7 days
• Expedited review for security-critical updates