1. Apps
  2. Import package

Apps

Import package

Import one reviewed Lantern package directory into governed inventory.

Reviewed package

Choose one package directory.

Lantern validates the manifest and referenced files, stores the reviewed snapshot, signs the reviewed runtime contract, and then adds the version to admin inventory.

Open reference apps Back to apps

Upload

Send the exact reviewed artifact.

Use the package directory itself, not a zip file or a rewritten export. Lantern expects the package root to contain manifest.json.

Choose the app folder so Lantern receives the reviewed file tree exactly once.

Canonical shape

Keep the package browser-first.

The reviewed package root should look like this baseline layout before you add optional scoring, grading, or evidence files.

manifest.json
dist/index.html
content/activity.json
preview/fixtures.json
preview/tests.json

What happens next

1. Review contract

Lantern checks the manifest, entrypoint, and referenced reviewed files.

2. Immutable snapshot

Lantern stores the reviewed snapshot under var/packages/<app-id>/<version>/....

3. Admin inventory

The package version lands in app inventory for approval, governed launch, and LMS setup.