---
title: "H5p"
description: "This repository is H5P's framework core: the PHP classes that validate, store and serve .h5p packages, plus the JavaScript that boots content in the browser and dispatches its events. It is not an application. It has no user interface, no installer and no authoring screen of its own — platforms implement H5PFrameworkInterface and the Moodle, WordPress and Drupal plugins are where an author actually meets it."
canonical_url: "https://scorm-tools.com/tools/h5p"
last_updated: "2026-10-31T10:22:00.520Z"
---

This repository is H5P's framework core: the PHP classes that validate, store and serve `.h5p` packages, plus the JavaScript that boots content in the browser and dispatches its events. It is not an application. It has no user interface, no installer and no authoring screen of its own — platforms implement `H5PFrameworkInterface` and the Moodle, WordPress and Drupal plugins are where an author actually meets it.

Its value to a directory reader is as the thing under the H5P you already use. If you are writing an integration for a platform H5P does not yet support, or debugging why a content type behaves differently on Moodle than on WordPress, this is the code that decides.

One correction matters more than the description. H5P is frequently described as having "SCORM export paths"; this repository has none, and the xAPI it emits stops at a JavaScript event. Both are the host platform's responsibility, and the answer differs by platform. If you want SCORM output from H5P, you want Lumi or an equivalent wrapper, and you will get SCORM 1.2.

Maintenance is solid: Joubel commit regularly, with the most recent push in August 2026. Eighty-eight open issues against 149 stars is normal for a library whose users mostly arrive through a plugin and never see the repository. Licensing is GPL-3.0 — the readme explains it is GPL because of the HTML purifier it embeds, which is worth knowing before you build a proprietary integration around it.