validate-extension-submission

Extension Index submission validation inspects your repository structure, metadata files, and URL accessibility for homepage, icon, and screenshots. It confirms required files like CMakeLists.txt and LICENSE are present and provides a concise report with remediation guidance for submission readiness.

Required files for Extension Index submission include CMakeLists.txt, LICENSE, and README.md. The validation also checks for metadata files like CONTRIBUTORS, DESCRIPTION, HOMEPAGE, ICONURL, and SCREENSHOTURLS to confirm the repository meets all submission requirements.

An Extension JSON file is not mandatory for submission validation, but if present, the validator checks its conformity to the current schema. This ensures any included Extension JSON meets the required structural standards for the Extension Index.

Submission validation fails on URL accessibility when the links for HOMEPAGE, ICONURL, or SCREENSHOTURLS are unreachable. The validator checks these URLs to ensure all extension resources are publicly available and accessible for the Extension Index.

You can check repository health before submitting by validating indicators like the 3d-slicer-extension topic, license type, and URL accessibility for homepage, icon, and screenshots. The validator provides a concise report with remediation guidance to streamline Extension Index submissions.

The best way to prepare an extension for Extension Index submission is to run a validation script that inspects repository structure, metadata fields, licensing, and URL accessibility. This proactive check prevents delays and back-and-forth remediation during the submission process.