Match the requested library line
A content package identifies dependencies by machine name and major/minor version. The target list in this tool uses that same shape, with an optional patch number. Copy installed values from the target administrator instead of guessing from a content type’s marketing name or the newest release online.
A package can bundle its dependencies, rely on the destination to provide them, or contain both a main library and supporting libraries. The report distinguishes these cases so that a missing archive folder is not automatically described as a broken lesson.
Make installation permissions explicit
A user allowed to upload content may not be allowed to install library code. Confirm the target policy before migration. When a required version is bundled but absent from the inventory, the report identifies an installation step rather than declaring that the destination is ready. An older supplied patch is also highlighted for administrator review.
- Compare exact names, including capitalization.
- Keep separate major/minor lines separate.
- Check both runtime and editing dependencies.
- Use the H5P Core API version for a core comparison, not the LMS version.
Verify after the administrator resolves dependencies
Export or refresh the target inventory, run the comparison again and import into a test activity. Open the editor as well as the learner view if the lesson will be maintained there. Code and integration behavior are outside this static checker, so the final test must use the real target installation.