---
title: "Elearning Module Parser"
description: "This is the ingest half of a SCORM platform, packaged as a Java 17 library. Point it at a zip, a directory or an S3 prefix and it works out which of five formats it is holding — SCORM 1.2, SCORM 2004, AICC, cmi5 or xAPI/TinCan — then returns typed metadata with consistent accessors for title, launch URL, structure and mastery data. That normalisation is the actual value: without it, every format needs its own parsing path and its own set of edge cases before your application can do anything useful with an upload."
canonical_url: "https://scorm-tools.com/tools/elearning-module-parser"
last_updated: "2026-10-31T10:22:02.422Z"
---

This is the ingest half of a SCORM platform, packaged as a Java 17 library. Point it at a zip, a directory or an S3 prefix and it works out which of five formats it is holding — SCORM 1.2, SCORM 2004, AICC, cmi5 or xAPI/TinCan — then returns typed metadata with consistent accessors for title, launch URL, structure and mastery data. That normalisation is the actual value: without it, every format needs its own parsing path and its own set of edge cases before your application can do anything useful with an upload.

The audience is narrow and obvious. If you are building or maintaining a JVM-based LMS, a content pipeline or QA tooling that accepts course packages, this saves you a fortnight of XML archaeology. If you are not on the JVM, it is not for you, and there is no CLI to borrow.

Be clear about the boundary. Nothing here plays content, tracks a learner, or implements a run-time. The same author's scorm-again covers the browser side, and the two are designed to sit either end of the same system.

It is young — first commit November 2024 — and has very few stars, but it is published to Maven Central, versioned properly, and pushed within the last week. Judge it on the release discipline rather than the star count.