grunt-scorm-manifest
Grunt task that writes an imsmanifest.xml for a single-SCO package
The facts
- Licence
- MIT — OSI approved
- Pricing
- Open source Price source for grunt-scorm-manifest, opens in a new tab
- Deployment
- Embedded in your own application
- Platforms
- Command line · Library
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 | Passing version '1.2' sets schemaversion to 1.2 and switches the resource attribute to the lower-case adlcp:scormtype the 1.2 schema requires. | |
| SCORM 20043rd edition | Yes | editor-checked · 24 Aug 2026— source, opens in a new tab | The task hard-codes the schemaversion string '2004 3rd Edition'. There is no 4th Edition option — '2004' and '2004v3' both produce a 3rd Edition manifest. | |
| xAPI | Not stated | — | — | — |
| cmi5 | Not stated | — | — | — |
| 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
This is a Grunt plugin that generates an imsmanifest.xml for a single-SCO course, published by Ray Gesualdo in 2013 and never revised: the sole release is v0.2.0, and the README carries an explicit "No Maintenance Intended" badge. The last commit to the repository was in 2016.
What it does, it does in about a hundred readable lines. You give it a course id, a title, a launch page and a file glob; it walks the matched files, writes the resource list, and emits either a SCORM 1.2 manifest or a "2004 3rd Edition" one. The only structural difference between the two is the schema version string and the casing of the adlcp:scormtype attribute, which is exactly the trap it exists to spare you.
The reasons not to depend on it are practical rather than moral. Grunt itself is largely out of use, the required version is ~0.4.2, there is no 2004 4th Edition path, and nothing beyond one SCO is expressible. Anyone building packages in a modern pipeline should reach for a maintained packager instead.
Its lasting value is as a reference. If you want to see the minimum viable manifest for both SCORM generations, side by side, with the version-specific gotchas isolated in one switch statement, this file is a clearer read than the ADL specification.
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