SCOBot
SCORM 1.2 and 2004 content wrapper with a mock LMS for working offline
The facts
- Licence
- CC-BY-SA-4.0
- Pricing
- Open source Price source for SCOBot, opens in a new tab
- Deployment
- Embedded in your own application
- Platforms
- Library · Web
- Vendor
- Cybercussion Interactive, LLC
- Documentation
- github.com/cybercussion/SCOBot/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 | editor-checked · 24 Aug 2026— source, opens in a new tab | The runtime branches on getAPIVersion() === '1.2' throughout SCOBot.js — interaction encoding, latency and timestamp formats, status persistence. | |
| SCORM 20042nd, 3rd, 4th editions | Yes | editor-checked · 24 Aug 2026— source, opens in a new tab | findAPI() discovers window.API_1484_11 and the 2004 data model is the library's native target. The specific list of editions (2nd, 3rd, 4th) is the README's claim; the code does not branch per edition. | |
| xAPI | No | editor-checked · 24 Aug 2026 | — | |
| cmi5 | No | editor-checked · 24 Aug 2026 | — | |
| 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
SCOBot is a JavaScript wrapper that sits between courseware and the SCORM run-time API, so that content authors write setInteraction() and setBookmark() rather than hand-building cmi.interactions.3.learner_response strings. It has been maintained by Cybercussion since 2009 and reached version 5 as a rewrite in ES modules with a Vite build, ESM and UMD bundles, and Vitest tests.
Its distinguishing feature is the polyfill layer. The same course code runs against SCORM 1.2 and 2004 because the library translates the data model in both directions — response encoding, latency and timestamp formats, single lesson_status versus split completion and success. If you ship one course to clients on different LMS generations, that is the reason to choose it over a thinner wrapper.
It is not a packager, a player or a test harness. It produces no manifest, and the bundled mock LMS is for development rather than conformance checking. Nor is it a good fit if you only ever target 2004 and are comfortable with the raw API; the abstraction is then overhead.
Maintenance is healthy for a single-vendor project: commits through 2026, CI running, an active companion player. The licence is the thing to check first — CC-BY-SA-4.0 is a content licence applied to code, and its ShareAlike terms are not what most procurement processes expect.
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