SCORM-Manifests
Boilerplate imsmanifest.xml files for single-SCO SCORM 1.2 and 2004 packages
The facts
- Licence
- No licence — The repository ships no licence file, so no rights are granted.
- Pricing
- Open source
- Deployment
- Embedded in your own application
- Platforms
- Library
- Vendor
- Philip Hutchison
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 | Manifest declares schema "ADL SCORM" / schemaversion "1.2" and ships the four SCORM 1.2 XSDs in a SCORM-schemas subfolder. | |
| SCORM 20044th edition | Yes | editor-checked · 24 Aug 2026— source, opens in a new tab | schemaversion is literally "2004 4th Edition"; the adlseq, adlnav and imsss namespaces are declared and the matching schemas are bundled. No 2nd or 3rd Edition variant is provided. | |
| xAPI | No | editor-checked · 24 Aug 2026 | — | |
| cmi5 | No | editor-checked · 24 Aug 2026 | — | |
| AICC | No | editor-checked · 24 Aug 2026 | — | |
| 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
Two directories, each containing an imsmanifest.xml and the ADL schemas it references: one for SCORM 1.2, one for SCORM 2004 4th Edition. Both are written for a single-SCO course whose entry point is index.html, and the readme lists the five or six strings you need to change — course identifier, version, organisation code, and the two title elements.
The useful detail is structural. The XSDs live in a SCORM-schemas/ subfolder with xsi:schemaLocation adjusted accordingly, rather than being dumped at the root of the zip as most examples do. A SCORM 2004 package carries about a dozen schema files, and pushing them out of the root makes it readable without upsetting LMSs that validate against them.
Who it is for: anyone assembling a package by hand or scripting one, who wants a manifest that is known-good rather than one reverse-engineered from an authoring tool's output. It is not a packager — nothing zips, validates or checks that your href values exist — and it does not cover multi-SCO organisations, sequencing rules or metadata, which is where manifests actually get difficult.
Maintenance state is unambiguous: last commit March 2017, fourteen stars, no open issues. That matters less than it usually would, because the SCORM 1.2 and 2004 4th Edition content packaging schemas have not changed since 2009. Treat it as a stable reference rather than a dependency, copy the two files into your own repo, and do not expect anyone to answer an issue.
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