---
title: "Pipwerks Scorm Manifests"
description: "Two directories, each containing an imsmanifest.xml and the ADL schemas it references: one for SCORM 1.2, one for SCORM 2004 4th Edition. Both are written for a single-SCO course whose entry point is index.html, and the readme lists the five or six strings you need to change — course identifier, version, organisation code, and the two title elements."
canonical_url: "https://scorm-tools.com/tools/pipwerks-scorm-manifests"
last_updated: "2026-10-31T10:22:01.592Z"
---

Two directories, each containing an `imsmanifest.xml` and the ADL schemas it references: one for SCORM 1.2, one for SCORM 2004 4th Edition. Both are written for a single-SCO course whose entry point is `index.html`, and the readme lists the five or six strings you need to change — course identifier, version, organisation code, and the two title elements.

The useful detail is structural. The XSDs live in a `SCORM-schemas/` subfolder with `xsi:schemaLocation` adjusted accordingly, rather than being dumped at the root of the zip as most examples do. A SCORM 2004 package carries about a dozen schema files, and pushing them out of the root makes it readable without upsetting LMSs that validate against them.

Who it is for: anyone assembling a package by hand or scripting one, who wants a manifest that is known-good rather than one reverse-engineered from an authoring tool's output. It is not a packager — nothing zips, validates or checks that your `href` values exist — and it does not cover multi-SCO organisations, sequencing rules or metadata, which is where manifests actually get difficult.

Maintenance state is unambiguous: last commit March 2017, fourteen stars, no open issues. That matters less than it usually would, because the SCORM 1.2 and 2004 4th Edition content packaging schemas have not changed since 2009. Treat it as a stable reference rather than a dependency, copy the two files into your own repo, and do not expect anyone to answer an issue.