---
title: "Rescorm"
description: "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."
canonical_url: "https://scorm-tools.com/tools/rescorm"
last_updated: "2026-10-31T10:22:01.247Z"
---

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.