Package structure gate
Five structural ZIP checks passed for manifest schemas, resource links, SCORM 2004 objectives and dual-SCO structure. This is package-level evidence, not a named-LMS result.
Evidence: 27 September 2026 · build b55d9835
This page lists exactly what has been tested, on which platform version, on which date, and what hasn't yet. A cell only says “verified” when we hold recorded evidence for it: no extrapolation, no “should work”.
| LMS | Version tested | SCORM versions | Date | Status |
|---|---|---|---|---|
| SCORM Cloud (Rustici) 124 of 124 flag-pack checks passed on the reference platform. This historical result covers its recorded build and test scope; each new release still needs its own regression evidence. Read the dated test record | v2 test API; runtime engine version not captured | SCORM 2004 4th Edition and 1.2 | 2026-07-20 | Verified |
| Blackboard Ultra Both editions imported, launched, resumed and reported 100/100 plus completion in one authorised course. This is scoped pilot evidence; the formal named-platform gate remains pending. Read the dated test record | Server build unavailable; observed UI assets uiv4000.21.0-rel.43_1fb0f29 | SCORM 2004 4th Edition and 1.2 | 2026-09-27 | Pending evidence |
| Moodle No formal executed Moodle run is recorded in the ledger. The earlier local-Docker setup was blocked; current tenant access and version must be established before testing. Read the dated test record | No Intle tenant/version test recorded | SCORM 1.2; verify any third-party 2004 engine separately | Not recorded | Pending evidence |
| Canvas No formal executed Canvas run is recorded. An authorised institution/account and enabled SCORM integration are required. Read the dated test record | No Intle tenant/version test recorded | Confirm the institution's enabled SCORM tool and editions | Not recorded | Pending evidence |
Recorded package checks
These local package-level results were recorded against the dated build shown below. Re-run them for a newer release before treating that release as covered:
Five structural ZIP checks passed for manifest schemas, resource links, SCORM 2004 objectives and dual-SCO structure. This is package-level evidence, not a named-LMS result.
Evidence: 27 September 2026 · build b55d9835
Ten local SCORM API-stub scenarios passed. Both editions restored position and answers; all tested compression stages respected their 4,096-character (1.2) and 64,000-character (2004) caps. Reduced payloads can omit answer detail. This tests the recorded package build, not the current release or another LMS.
Evidence: 27 September 2026 · build b55d9835
Test it yourself
The course content comes from the recorded compliance-module fixture and includes a scored final assessment. These downloads use the current player. Test completion, scores and resume behaviour in your own LMS before rollout. They are provided for your trial and are not identified as the exact July test packages.
No. intle packages run inside the LMS frame and never call window.open, so default browser settings with the popup blocker enabled are fine. If your LMS launches courses in a new window, the runtime also searches the opener window for the SCORM API; use the sample package and matrix evidence before treating a named LMS as verified.
The pass mark you set in intle is written into the package manifest: SCORM 2004 packages carry a completion threshold and a primary objective with a minimum measure; SCORM 1.2 packages carry adlcp:masteryscore. At runtime the package also reports the score and passed/failed status itself, so use the evidence matrix and your own upload test to confirm how a specific LMS surfaces it.
Some LMS configurations enforce SCORM 1.2's 4KB resume-storage limit even on 2004 packages. intle packages handle this with staged compression: full answers first, then truncated answers, then position-and-score-only. If your LMS has that constraint, prefer the SCORM 1.2 download, which is engineered around the smaller limit.
Interactive-video sections embed a YouTube player in the LMS frame and need the learner's network and LMS content-security policy to permit it. If that player is blocked, the video cannot be watched and timed questions cannot be relied on; a transcript is available only when one was supplied with the section. Test a video package on your learner network before rollout. The sample below has no embedded video; to test video behaviour, generate a package from a YouTube link or add a video in the editor.
Core course code and many activities are bundled in the SCORM zip, but do not assume every package works offline. URL-referenced logos, external video and captions need network access; tracked analytics, verified identity and live collaboration also depend on services outside the zip. Check the delivery report and test the exact export on your network. Offline LMS tracking is not guaranteed.
Check your LMS vendor's supported versions and the evidence matrix first. Where both are supported, SCORM 2004 4th Edition can report richer data such as per-topic objectives and separate completion and pass status; SCORM 1.2 is useful where the platform requires it or enforces tighter resume-data limits. Test the supplied sample in your own configuration before rollout.
Every plan exports both SCORM versions from the same content. New to LMS uploads? Start with the step-by-step delivery guide.