scorm-kit
A nine-command CLI that lints, diffs and audits SCORM packages before upload
The facts
- Licence
- MIT — OSI approved
- Pricing
- Open source
- Deployment
- Embedded in your own application
- Platforms
- Command line
Standards support
Every line says where the claim came from. We do not test conformance ourselves and we issue no badge of our own.
| Standard | Supported | Provenance | Checked | Note |
|---|---|---|---|---|
| SCORM 1.2 | Yes | editor-checked · 24 Aug 2026— source, opens in a new tab | The linter requires schema "ADL SCORM" and schemaversion 1.2, and the `mock` runtime exposes `window.API` only. SCORM 1.2 is the whole target. | |
| SCORM 2004 | No | editor-checked · 24 Aug 2026 | A 2004 package is reported as an error by `lint`, and the mock runtime does not expose `API_1484_11`. | |
| xAPI | No | editor-checked · 24 Aug 2026 | No xAPI client. The `rum` command posts its own JSON beacons to an endpoint you supply, not xAPI statements to an LRS. | |
| cmi5 | Yes | editor-checked · 24 Aug 2026— source, opens in a new tab | `cmi5 validate` and `cmi5 lint` check cmi5.xml structure — courseStructure root, IRI-shaped ids, launchMethod and moveOn enumerations, masteryScore range, AU launch URLs resolving inside the package. `cmi5 convert` wraps a SCORM 1.2 package as a cmi5 AU. This is packaging-level support; nothing here runs a cmi5 session. | |
| 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
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.
Alternatives to scorm-kit
Chosen by hand because they solve the same problem, not because they share a keyword.
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