---
title: "Scorm To Xapi Wrapper"
description: "A migration aid from ADL, from the period when organisations were being encouraged to move from SCORM to xAPI without reauthoring their content. You replace the standard APIWrapper.js in each SCO with ADL's modified copy, add two script tags, and every run-time call the course makes is mirrored into an LRS as an xAPI statement following the draft xAPI SCORM Profile."
canonical_url: "https://scorm-tools.com/tools/scorm-to-xapi-wrapper"
last_updated: "2026-10-31T10:22:01.797Z"
---

A migration aid from ADL, from the period when organisations were being encouraged to move from SCORM to xAPI without reauthoring their content. You replace the standard `APIWrapper.js` in each SCO with ADL's modified copy, add two script tags, and every run-time call the course makes is mirrored into an LRS as an xAPI statement following the draft xAPI SCORM Profile.

For a library of legacy SCORM courses that must keep working in an existing LMS while feeding a new analytics store, the idea is still the right one, and the mapping is worth reading if you are implementing that translation yourself.

As deployable code it has aged badly, and its own repository says so. The archive flag was set by ADL, the last commit to `master` was March 2017, the SCORM 1.2 wrapper carries an unresolved out-of-date warning, the profile it implements never left draft, and LRS credentials sit in a file shipped to the browser. There is no licence file, which rules it out of client work regardless of the technical state.

Ninety-nine stars mean it remains the first result people find. Treat it as documentation of an approach — read the mapping, then implement it against a maintained xAPI client.