---
title: "Simple Scorm Packager"
description: "The job here is small and well defined: point it at a directory of built web files, give it a title, a version, a language and a mastery score, and it writes imsmanifest.xml, copies in the schema definition files and zips the lot. It works either programmatically or through a CLI, which is what makes it useful — packaging becomes an npm script that runs after the bundler rather than a manual step someone forgets before a release."
canonical_url: "https://scorm-tools.com/tools/simple-scorm-packager"
last_updated: "2026-10-31T10:22:03.536Z"
---

The job here is small and well defined: point it at a directory of built web files, give it a title, a version, a language and a mastery score, and it writes `imsmanifest.xml`, copies in the schema definition files and zips the lot. It works either programmatically or through a CLI, which is what makes it useful — packaging becomes an npm script that runs after the bundler rather than a manual step someone forgets before a release.

The metadata options are unusually thorough for a tool of this size: LOM description, keywords, typical duration, a vCard for the author, and structured requirements entries. If a client's LMS is fussy about manifest metadata, that matters.

It is not an authoring tool and does not touch the run-time API. Your content still has to call SCORM itself, through a wrapper of your choosing.

The important fact for anyone deciding today is that the repository was archived by its owner. The 2026 commits are Dependabot merges for transitive dependency advisories, not development, and npm has stood at 0.2.7 since June 2022. With 74 stars it remains the most-referenced Node packager of its kind, and archived code that only writes XML and zips files ages better than most — but no bug you find will be fixed upstream, and a fork is the realistic path if you need a change.