---
title: "Grunt Scorm Manifest"
description: "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."
canonical_url: "https://scorm-tools.com/tools/grunt-scorm-manifest"
last_updated: "2026-10-31T10:22:02.474Z"
---

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.