RESCORM
React boilerplate that ships SCORM tracking alongside the application code
The facts
- Licence
- MIT — OSI approved
- Pricing
- Open source
- Deployment
- Embedded in your own application
- Platforms
- Library · Web
- Documentation
- github.com/agordillo/RESCORM/wiki — opens in a new tab
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 | vendor-stated— source, opens in a new tab | Listed in the project README's feature table. We read the README and the repository layout but did not run a package against an LMS. | |
| SCORM 20044th edition | Yes | vendor-stated— source, opens in a new tab | The README states "SCORM 1.2 and SCORM 2004 4th Edition support". Not confirmed against the running code. | |
| xAPI | No | vendor-stated | — | |
| cmi5 | No | vendor-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
RESCORM is a project skeleton rather than a library: clone it and you get a React application wired to Redux, React Router, i18n, SASS, Jest and Enzyme, with SCORM communication already plumbed in and a webpack build that produces something an LMS can launch. Its documentation lives in the repository wiki rather than the README.
The idea is sound and still uncommon — most SCORM front-end work involves bolting a tracking wrapper onto an app that was never designed for it, and starting from a template that already knows about launch, resume and commit removes a genuinely fiddly day of work.
The problem is the vintage. The pinned stack is React 16.0, React Router 4 and webpack 3, and the last commit was December 2022. Adopting it today means adopting a 2017-era toolchain and then migrating it yourself, which is more work than lifting the SCORM layer out and dropping it into a current React setup. Twenty-one issues are open against forty-nine stars.
Read it for the tracking plumbing and the packaging build, which are the parts that age well. Do not treat it as a starting template for new work, and note that we are relying on the README for its standards claims rather than a run against a conformance suite.
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