mod_scormremote
Serve a SCORM package from your Moodle into someone else's LMS via a thin wrapper SCO
The facts
- Licence
- GPL-3.0-or-later — OSI approved
- Pricing
- Open source
- Deployment
- Self-hosted
- Platforms
- LMS plugin
- Vendor
- Catalyst IT Australia
- Headquarters
- Australia
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 generated wrapper SCO is SCORM 1.2. It sets window.API to a Scorm12API instance from scorm-again and bridges the LMS* calls back across postMessage. | |
| SCORM 2004 | No | editor-checked · 24 Aug 2026— source, opens in a new tab | Only the scorm12 build of scorm-again is vendored, and the bridge never defines API_1484_11. The wrapper the remote LMS receives therefore speaks SCORM 1.2, whatever version the underlying course is. | |
| xAPI | No | editor-checked · 24 Aug 2026 | — | |
| cmi5 | No | editor-checked · 24 Aug 2026 | — | |
| AICC | No | editor-checked · 24 Aug 2026 | — | |
| 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 solves a specific commercial problem: you sell or licence SCORM content, and handing over a zip means handing over the asset. mod_scormremote inverts that. The client's LMS receives a wrapper SCO that loads the real course from your Moodle in a sandboxed iframe and relays the SCORM API across domains with postMessage. You keep the content, you can replace it in place, and you get usage back — accounts, enrolments and completion appear in your Moodle as remote learners work through it.
The seat-limiting is the other half of the pitch. Clients are defined by their domains, tiers cap how many seats each client may consume, and a single wrapper file identifies which client is using it from the requesting domain. That is closer to a licensing system than an activity module, and it is why the plugin exists at all.
Know the constraint before you build on it: the wrapper is SCORM 1.2. It vendors only the scorm12 build of scorm-again and never defines API_1484_11, so 2004-specific tracking on the remote side is not available. Frame embedding must also be permitted at both ends, which not every corporate client's LMS will allow.
Catalyst maintain it against a single MOODLE_39_STABLE branch, with CI and commits as recent as July 2026 — a supported vendor plugin rather than a hobby project, though support is explicitly best-effort unless you sponsor work.
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