This is an XBlock to display SCORM content within the Open edX LMS and Studio. It will save student state and report scores to the progress tab of the course. Currently supports SCORM 1.2 and SCORM 2004 standard.
This XBlock was initially developed by Raccoon Gang and published as edx_xblock_scorm. It was later improved, published on Pypi and relicensed as AGPLv3 thanks to the support of Compliplus Ltd.
This XBlock is not compatible with its ancestor: older xblocks cannot be simply migrated to the newer one. However, this xblock can be installed next to the other one and run on the same platform for easier transition.
Features
Full SCORM data student reports for staff users
Fullscreen display on button pressed
Optional display in pop-up window
Integrated grading, compatible with rescoring
Optional custom width navigation menu interpreted from manifest file
Compatibility with Django storages, customizable storage backend
Installation
This XBlock was designed to work out of the box with Tutor (Ironwood release). It comes bundled by default in the official Tutor releases, such that there is no need to install it manually.
For non-Tutor platforms, you should install the Python package from Pypi:
pip install openedx-scorm-xblock
In the Open edX native installation, you will have to modify the files /edx/etc/lms.yml and /edx/etc/studio.yml. Replace
X_FRAME_OPTIONS: DENYBy
X_FRAME_OPTIONS: SAMEORIGINUsage
In the Studio, go to the advanced settings of your course (“Settings” 🡒 “Advanced Settings”). In the “Advanced Module List” add “scorm”. Then hit “Save changes”.
Go back to your course content. In the “Add New Component” section, click “Advanced”, and then “Scorm module”. Click “Edit” on the newly-created module: this is where you will upload your content package. It should be a .zip file containing an imsmanifest.xml file at the root. The content of the package will be displayed in the Studio and the LMS after you click “Save”.
Advanced configuration
Asset url
By default, SCORM modules will be accessible at “/scorm/” urls and static assets will be stored in “scorm” media folders – either on S3 or in the local storage, depending on your platform configuration. To change this behaviour, modify the xblock-specific LOCATION setting
XBLOCK_SETTINGS["ScormXBlock"] = {
"LOCATION": "alternatevalue",
}Custom storage backends
By default, static assets are stored in the default Open edX storage backend.
To override this behaviour, you should define a custom storage function. This function must take the xblock instance as its first and only argument. For instance, you can store assets in different directories depending on the XBlock organization with
def scorm_storage(xblock):
from django.conf import settings
from django.core.files.storage import get_storage_class
from openedx.core.djangoapps.site_configuration.models import SiteConfiguration
subfolder = SiteConfiguration.get_value_for_org(
xblock.location.org, "SCORM_STORAGE_NAME", "default"
)
storage_location = os.path.join(settings.MEDIA_ROOT, subfolder)
return get_storage_class(settings.DEFAULT_FILE_STORAGE)(
location=storage_location, base_url=settings.MEDIA_URL + "/" + subfolder
)
XBLOCK_SETTINGS["ScormXBlock"] = {
"STORAGE_FUNC": scorm_storage,
}This should be added both to the LMS and the CMS settings. Instead of a function, a string that points to an importable module may be passed
XBLOCK_SETTINGS["ScormXBlock"] = {
"STORAGE_FUNC": "my.custom.storage.module.get_scorm_storage_function",
}Note that the SCORM XBlock comes with extended S3 storage support out of the box. See the following section:
Accessing assets directly from storage
By default, scorm will proxy assets through the LMS. This is done for security and to make the backend generic enough to be used with different storage backends. However, to access assets directly from the default storage backend, add the following to the ScormXBlock settings:
XBLOCK_SETTINGS["ScormXBlock"] = {
"PROXY_ASSETS_LMS": False,
}Scorm will now use the configured storage backends default url method instead of proxying the data through the LMS. The url method must be defined on the configured storage class for this to work correctly.
S3 storage
The SCORM XBlock will serve static assets from S3 if it is configured as the default storage for Open edX.
However, to configure S3 storage specific to scorm xblock, add the following to your LMS and CMS settings
XBLOCK_SETTINGS["ScormXBlock"] = {
"STORAGE_FUNC": "openedxscorm.storage.s3"
}You may define the following additional settings in XBLOCK_SETTINGS["ScormXBlock"]:
S3_BUCKET_NAME (default: AWS_STORAGE_BUCKET_NAME): to store SCORM assets in a specific bucket separate from the rest of your Open edX assets.
S3_QUERY_AUTH (default: True): boolean flag (True or False) for query string authentication in S3 urls. If your bucket is public, set this value to False. But be aware that in such case your SCORM assets will be publicly available to everyone.
S3_EXPIRES_IN (default: 604800): time duration (in seconds) for the presigned URLs to stay valid. The default is one week.
These settings may be added to Tutor by creating a plugin:
from tutor import hooks
hooks.Filters.ENV_PATCHES.add_item(
(
"openedx-common-settings",
"""
XBLOCK_SETTINGS["ScormXBlock"] = {
"STORAGE_FUNC": "openedxscorm.storage.s3",
"S3_BUCKET_NAME": "mybucket",
...
}"""
)Development
Run unit tests with:
$ pytest /mnt/openedx-scorm-xblock/openedxscorm/tests.py
Troubleshooting
This XBlock is maintained by Syed Ali Abbas from Edly. Community support is available from the official Open edX forum. Do you need help with this plugin? See the troubleshooting section from the Tutor documentation.
Versioning
This XBlock follows an independent MAJOR.MINOR.PATCH versioning scheme and is not tied to the Open edX or Tutor release version. While earlier releases tracked the Tutor version, this package is a standalone XBlock with no dependency on Tutor. To avoid downgrading the already-published version, 19 is retained as the current major version, and the project is versioned independently from this release onward.
Contributing
We welcome contributions to this repo! Here are the guidelines for contributing:
Pull Requests
For changes to the SCORM XBlock, open a pull request on this repository. Take care to target your pull request to the proper branch:
Target master if your change is compatible with the latest official Open edX release and it carries no major backwards-incompatibility nor risk of regression. This ensures that the latest stable release benefits from bug fixes and incremental improvements. Once merged, your change will automatically be forward-ported to nightly.
Target nightly if your change is only compatible with Open edX’s master branches and/or your change would be disruptive to production site operators. If merged, your change will be incorporated into master at the time of the next named Open edX release.
At the beginning of each Open edX named release testing period, we split off from nightly a special pending release branch (e.g., sumac or teak). If your change is necessary for that pending release, merge it to said branch. At the end of the testing period, the pending branch will be merged into master and deleted. As with any set of changes merged to master, they will then be forward-ported to nightly.
Changelog Entry
Create a changelog entry for significant changes (excluding reformatting or documentation) by running:
make changelog-entry
Edit the newly created file following the default formatting instructions in the generated file.
Commit Messages
Write clear Git commit titles and messages. Detail the rationale for your changes, the issue being addressed, and your solution. Include links to relevant forum discussions and describe your use case. Detailed explanations are valuable. For commit titles, follow conventional commits guidelines.
Additionally, if your pull request addresses an existing GitHub issue, include ‘Close #XXX’ in your commit message, where XXX is the issue number.
License
This work is licensed under the terms of the GNU Affero General Public License (AGPL).
4 maintainers
Metadata
4 maintainers
Release files for openedx-scorm-xblock 19.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| openedx_scorm_xblock-19.0.4.tar.gz | 46.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openedx_scorm_xblock-19.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 102.9 kB
Release files / openedx_scorm_xblock-19.0.4.tar.gz
| Download URL | openedx_scorm_xblock-19.0.4.tar.gz |
|---|---|
| Size | 46.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40efd37ada9cb6f154dcb3e5ac444a4077c391fc920396f4b8e9c404dd89f69f
|
|
BLAKE2b-256 checksum How to use checksums |
6f0dfa4526f2d87e64354d6437bba96b195aa0c063c4cecbe3b9f232a24dff30
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 12, 2026.
Transparency logRelease files / openedx_scorm_xblock-19.0.4-py3-none-any.whl
| Download URL | openedx_scorm_xblock-19.0.4-py3-none-any.whl |
|---|---|
| Size | 56.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
19592fb6001902f3a4e84ab892d5e3df69e38072685d129cd9cb78aaca727e03
|
|
BLAKE2b-256 checksum How to use checksums |
539a7dd5fb8425e39183e31cd75afd1e760400a84e9167d32caef6a4327be659
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 12, 2026.
Transparency log
