Skip to content

simple-scorm-packager

Node package that turns a build directory into a conformant SCORM zip

Archived Last commit Checked · 24 Aug 2026

The facts

Licence
MIT — OSI approved
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.

Standards support for simple-scorm-packager, with the source of each claim and the date it was last confirmed.
Standard Supported Provenance Checked Note
SCORM 1.2 Yes editor-checked · 24 Aug 2026— source, opens in a new tabThe repository ships the SCORM 1.2 schema set (adlcp_rootv1p2, imscp_rootv1p1p2, imsmd_rootv1p2p1) and writes a matching manifest.
SCORM 20043rd, 4th editions Yes editor-checked · 24 Aug 2026— source, opens in a new tabSeparate schema directories for 2004 3rd and 4th Edition, including the imsss sequencing schemas. 2004 2nd Edition is not offered.
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

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.

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