Identity
SCORM version and edition, schema declaration, package size, and file count.
A training team can inherit a SCORM zip with no documentation, such as a vendor deliverable or an old course export. Before a migration or repair, the team needs to identify the SCORM version, SCO count, and launch file. The inspector answers these questions before the package enters a production LMS.
The inspector answers those questions from the package itself. It decodes the manifest into the same structures an LMS builds: the organization tree learners will see as a menu, the resource table with each launchable and its files, the dependency graph, and the resolved launch path with its parameters.
The inspector runs the validator checks and includes structural faults in the same report. Download the text or JSON report to attach the exact evidence to a support request.
The inspector reads the package locally in your browser. It reads metadata and does not upload or execute package content.