---
title: "Scorm Lms Dhodges47"
description: "An open-source demonstration LMS: register, upload a package, launch it in a built-in player, and see per-learner tracking. It is a Razor Pages application over Entity Framework Core and SQL Server, and its value is that the whole SCORM path is visible in a few files — a JavaScript adapter, one API controller, and a set of entity classes named directly after the CMI model (cmi_core, cmi_objectives, cmi_interactions, cmi_student_preference)."
canonical_url: "https://scorm-tools.com/tools/scorm-lms-dhodges47"
last_updated: "2026-10-31T10:22:01.642Z"
---

An open-source demonstration LMS: register, upload a package, launch it in a built-in player, and see per-learner tracking. It is a Razor Pages application over Entity Framework Core and SQL Server, and its value is that the whole SCORM path is visible in a few files — a JavaScript adapter, one API controller, and a set of entity classes named directly after the CMI model (`cmi_core`, `cmi_objectives`, `cmi_interactions`, `cmi_student_preference`).

That makes it a good way to learn what an LMS actually has to store, and a plausible starting point for an in-house .NET system where buying a platform is disproportionate. The author frames it that way too, and the framing is honest.

Treat the SCORM 2004 claim with care. The adapter registers an `API_1484_11` object, but the 2004 methods are aliases onto the 1.2 implementations, so 2004 content will initialise and talk while the model beneath it stays 1.2. There is no sequencing, no navigation model, no multi-tenancy, and the repository carries vendored `bower_components` including a full Font Awesome, so a clone is heavier than the code it contains.

Maintenance is real but light: 184 stars, a steady trickle of community pull requests, and a migration to .NET 8 in January 2026 contributed by a user. A useful reference implementation; not a product, and not a substitute for testing against the LMS your learners will use.
