---
title: "Scorm Debug"
description: "scorm_debug is one PHP script and two borrowed runtime harnesses. Point a web server at the folder, drop zips in, and it extracts each one, reads imsmanifest.xml to find the launch page, and gives you a link to open that page inside a SCORM 1.2 wrapper and another to open it inside a 2004 wrapper. php -S localhost:8080 and you are testing."
canonical_url: "https://scorm-tools.com/tools/scorm-debug"
last_updated: "2026-10-31T10:22:03.431Z"
---

scorm_debug is one PHP script and two borrowed runtime harnesses. Point a web server at the folder, drop zips in, and it extracts each one, reads `imsmanifest.xml` to find the launch page, and gives you a link to open that page inside a SCORM 1.2 wrapper and another to open it inside a 2004 wrapper. `php -S localhost:8080` and you are testing.

The audience is a developer who receives SCORM packages from other people and needs to see whether a course initialises, sets a status and commits, without the ceremony of uploading to an LMS or registering for a cloud service. For that narrow job the lack of ambition is the feature — there is nothing to configure and nothing to sign up for.

It is not a conformance tool and does not claim to be. No sequencing, no reporting, no persistence between runs, no validation of what the course writes. The 2004 harness is Claude Ostyn's from 2007, which is a testament to how well that wrapper was built and also an indication of how much has been maintained since.

The last commit was June 2019; there are twenty-two stars and one open issue. The licensing patchwork is the practical caution: three licences, no LICENSE file, and one of them share-alike.