Skip to content

@szenadam/scorm-api-wrapper

A TypeScript reimplementation of the pipwerks SCORM wrapper, published to npm

Stale · 45 mo Last commit Checked · 24 Aug 2026

The facts

Licence
MIT — OSI approved
Deployment
Embedded in your own application
Platforms
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 @szenadam/scorm-api-wrapper, 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 wrapper searches parent and opener windows for an `API` object and branches on a `1.2` case throughout get, set, status and commit.
SCORM 2004 Yes editor-checked · 24 Aug 2026— source, opens in a new tabFinds `API_1484_11` and branches on a `2004` case. The run-time API is the same across 2004 editions, so no edition is claimed here.
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

This is a single TypeScript file — one class, roughly 300 lines — that finds the SCORM API object in a parent or opener window and gives you initialize, get, set, status, save and quit over it. The README states plainly that it is a reimplementation of the widely-used pipwerks wrapper, and the repository keeps both of the original JavaScript files under references/ for comparison. It is not a fork: the logic was rewritten as a class with typed returns and private members, then tested with Jest.

The audience is narrow but real: a TypeScript project that wants the pipwerks behaviour without a declare module shim or a hand-written type file. If you do not need types, the original is better attended.

What it is not good for is anything beyond the run-time API. There is no packaging, no manifest generation, no sequencing, no offline queueing, and no handling of the LMS-specific quirks that make production SCORM integration awkward.

Weigh the maintenance state before adopting it. The last commit to master was a Dependabot merge in December 2022, npm shows version 1.1.1 from April 2022, and the project has eight stars and no open issues. Nothing here is broken, but nothing will be fixed either — treat it as source to read and vendor rather than a dependency to track.

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