Package Download
Download the SCORM package from SecureCodingHub and upload it to your Learning Management System.
Downloading the Package
Sign in as Org Admin
Open the SCORM page from the sidebar (Integrations → SCORM)
If SCORM has not been enabled for your organization yet, switch the Enabled toggle on first — package download is blocked until it is on
Pick a SCORM version (1.2 or 2004) from the version toggle
Click Download Package — the backend hits GET /api/sch/org/scorm/package?version=<1.2 or 2004> and streams back a .zip file
Upload the .zip into your LMS without extracting it
Package Contents
The downloaded archive is named securecodinghub-<orgSlug>-scorm12.zip or …-scorm2004.zip, depending on the version you chose. It contains three files:
| File | Purpose |
|---|---|
imsmanifest.xml | SCORM manifest describing the course structure. |
launcher.html | Launch page that initiates the SCORM session and embeds the call into the live SecureCodingHub app. |
scorm-bridge.js | JavaScript bridge that mediates between the LMS's SCORM API adapter and SecureCodingHub. |
Choosing a Version
| Feature | SCORM 1.2 | SCORM 2004 |
|---|---|---|
| LMS Compatibility | Very high (nearly universal) | High (most modern LMS) |
| Score Reporting | Basic (0-100 raw) | Enhanced (scaled, raw, min, max) |
| Suspend / Resume | Bookmark-based | Full suspend data |
| Recommendation | Use if unsure | Use if supported |
SCORM Settings in Admin Panel
Why the package is so small
The SecureCodingHub SCORM ZIP is intentionally lightweight — usually tens of kilobytes rather than the megabytes a packaged-content SCO would weigh. It contains only the SCORM manifest, the launch shell (launcher.html), and the bridge script that hands the LMS session over to the live SecureCodingHub platform. The actual training content, challenges, code editor, and feedback engine all stream from app.securecodinghub.com. Two things follow from that design.
First, you never have to redistribute a new SCORM package when new challenges, new languages, or content updates ship. The LMS continues to point at the same SCO, and the latest content appears the next time a learner launches it. Second, security review by the LMS administrator is straightforward: the package is small enough to audit by hand, and the bridge script is the only piece of executable code inside it.
Picking between SCORM 1.2 and SCORM 2004
Both packages share the same launch experience and the same training catalog. The difference is in how completion and score data are written back to the LMS. SCORM 1.2 reports a raw score between 0 and 100, a completion status of either incomplete or completed, and a single bookmark string for resume. SCORM 2004 adds a scaled score between 0.0 and 1.0, separate completion and success statuses, full suspend data for richer resume behaviour, and improved sequencing for organisations that want to control the order in which sub-modules unlock.
If your LMS administrator is unsure which version to deploy, SCORM 1.2 is the safer default — it is supported by virtually every LMS in production and the reporting fidelity is sufficient for most compliance use cases. Move to SCORM 2004 if your reporting policy requires distinct completion and success states, if you want to leverage the LMS's adaptive sequencing, or if your LMS vendor recommends it for new deployments.
Hosting the package on your own infrastructure
Some customers prefer to host the SCORM package on internal storage — for example, an SFTP-only LMS or an air-gapped training portal that pulls content from a controlled artefact store. In those cases the workflow is to download the package once from the SecureCodingHub admin console, hash it, store it in your artefact repository, and reference it from the LMS through your normal change-control process. SecureCodingHub does not rotate the SCORM bridge on a fixed schedule, so the same package can remain valid for the lifetime of the contract.
The launcher is generated server-side at download time, so the bridge URL it embeds is whatever App:BackendUrl the deployment was configured with. If your organization's deployment changes hostnames, re-download the package so the bridge points at the right host.