---
title: "Scorm Kit"
description: "scorm-kit is a build-pipeline CLI for SCORM 1.2 packages: nine subcommands covering static lint of the manifest and API usage, a WCAG 2.2 AA static audit, a semantic diff between two zips, a translation bundler, a local mock LMS, real-user-monitoring injection, a PII and tracker audit, cmi5 validation and SCORM-to-cmi5 wrapping, and a report command that aggregates three of those into one score. Everything takes --json and returns conventional exit codes, which is the point — it is designed to sit in CI rather than to be run by hand."
canonical_url: "https://scorm-tools.com/tools/scorm-kit"
last_updated: "2026-10-31T10:22:03.175Z"
---

scorm-kit is a build-pipeline CLI for SCORM 1.2 packages: nine subcommands covering static lint of the manifest and API usage, a WCAG 2.2 AA static audit, a semantic diff between two zips, a translation bundler, a local mock LMS, real-user-monitoring injection, a PII and tracker audit, cmi5 validation and SCORM-to-cmi5 wrapping, and a `report` command that aggregates three of those into one score. Everything takes `--json` and returns conventional exit codes, which is the point — it is designed to sit in CI rather than to be run by hand.

The interesting commands are the ones nobody else offers. Treating a package as a reviewable artifact — parsing the manifest, hashing the asset list, emitting a unified diff — is a good idea for teams who put courseware through pull requests. The privacy audit covers what a procurement review flags and a courseware vendor will not volunteer.

It is not an authoring tool, not a SCORM 2004 tool, and the a11y and privacy passes are static analysis, not a substitute for a manual audit.

The maintenance picture is the deciding factor. This is a single-maintainer project created in May 2026, last pushed in June, with no stars, no forks and one npm release. The code is clean and the tests exist, but a directory reader should treat it as a promising reference implementation to read and borrow from — or to vendor at a pinned commit — rather than something to make a client's release pipeline depend on this year.