---
title: "Node Scorm Packager"
description: "node-scorm-packager is a small Node module that takes a directory of finished HTML output, generates an imsmanifest.xml for it, copies the matching SCORM schema definition files alongside, and writes the result to a destination folder. You give it a version, a title, an organisation, an identifier, a mastery score and a starting page; it gives you a package layout. It was written to sit inside a Gulp build, and the README's second example is exactly that."
canonical_url: "https://scorm-tools.com/tools/node-scorm-packager"
last_updated: "2026-10-31T10:22:02.815Z"
---

node-scorm-packager is a small Node module that takes a directory of finished HTML output, generates an `imsmanifest.xml` for it, copies the matching SCORM schema definition files alongside, and writes the result to a destination folder. You give it a version, a title, an organisation, an identifier, a mastery score and a starting page; it gives you a package layout. It was written to sit inside a Gulp build, and the README's second example is exactly that.

It suits a team whose course is already a static web build and who want SCORM wrapping as a build step rather than a manual chore. It is deliberately narrow: no runtime, no API wrapper, no multi-SCO organisations, no sequencing, and — the part that catches people — no zip. You get a directory and have to compress it yourself.

The maintenance state is the deciding factor. The last commit was December 2018, npm still shows 0.0.9 from March 2016, and the project has seven stars and two open issues. Nothing here is broken, because the SCORM 1.2 and 2004 manifest formats have not moved since. But it is a frozen single-maintainer utility: read it, or vendor it, rather than depending on it receiving a fix.