laravel-scorm
Laravel package that unpacks SCORM zips and stores CMI tracking in your database
The facts
- Licence
- MIT — OSI approved
- Pricing
- Open source
- Deployment
- Embedded in your own application
- Platforms
- Library · LMS plugin
Standards support
Every line says where the claim came from. We do not test conformance ourselves and we issue no badge of our own.
| Standard | Supported | Provenance | Checked | Note |
|---|---|---|---|---|
| SCORM 1.2 | Yes | editor-checked · 24 Aug 2026— source, opens in a new tab | ScormManager reads <schemaversion> from the manifest and maps '1.2' to a SCORM 1.2 tracking model; ScormScoTracking persists the cmi.core elements. | |
| SCORM 20042nd, 3rd, 4th editions | Yes | editor-checked · 24 Aug 2026— source, opens in a new tab | The manifest parser accepts 'CAM 1.3', '2004 3rd Edition' and '2004 4th Edition' and collapses all three into a single scorm_2004 tracking model. There is no sequencing or navigation engine, so multi-SCO 2004 packages that rely on imsss rules will not behave as they do in a full LMS. | |
| xAPI | No | editor-checked · 24 Aug 2026 | — | |
| cmi5 | No | editor-checked · 24 Aug 2026 | — | |
| AICC | Not stated | — | — | — |
| LTI | Not stated | — | — | — |
- Claimed
- — the vendor states it. We have not confirmed it.
- Checked
- — an editor confirmed it on the date shown.
- Verified
- — an official registry lists it, and we link to the entry.
Editor's notes
laravel-scorm is the server-side half of SCORM support for a Laravel application: upload a package, and it extracts the zip to a configured disk (local or S3), parses imsmanifest.xml into SCO records, creates the migrations for the tracking tables, and stores each learner's CMI data as they work through the course. Configuration is a published config/scorm.php, with translatable runtime error messages.
It fits teams that already have a Laravel product with users, courses and a database, and want SCORM content to become one more trackable activity rather than a reason to buy an LMS. It is not a drop-in feature: the README's prerequisites include serving extracted content from a separate domain outside the application root, which is the right call for security but means infrastructure work before anything renders.
The gap to be clear about is 2004. Packages are detected and tracked, but the two-thousand-and-four story stops at the data model — no sequencing, no navigation requests, no rollup. Single-SCO courses behave; anything relying on imsss rules will not.
Maintenance is real but thin: pushed March 2026, forty-eight stars, thirty-seven forks, nine open issues, and a README that opens by asking for collaborators. One maintainer, actively responding — which is better than most packages in this category, and still a single point of failure.
Listed on scorm-tools.com
Maintainers and vendors are welcome to show the listing badge in a README or on a product page. It is free, it does not require a claim, and there is nothing to buy.
Get the embed code