Skip to main content

Evaluate a pack before installation

Find a pack, inspect its exact release, and preview its changes before allowing Luna to write project files.

Find available packs​

List the preferred latest release of each pack ID across configured sources:

luna discover

Search IDs, descriptions, and tags when you know the capability rather than the pack ID:

luna search guidelines

Add --versions 3 to either command when you need to compare older releases. The value can be from 1 through 10; results use descending Semantic Version order.

Inspect an exact release​

Pin the version while reviewing identity, attribution, parameters, and dependencies:

luna inspect [email protected]

Confirm the author, license, managed targets, required parameters, and referenced packs match what you intend to add. Review configured identities separately with luna sources list; pack IDs do not prove publisher identity.

luna validate <id>@<version> provides additional manifest and selected-file validation for packs in configured local or Git sources. An exact reference can validate a draft release; use --allow-draft to make drafts visible in discover or search results.

Preview project changes​

Run installation as a dry run with scripts disabled:

luna install [email protected] `
  --dry-run `
  --scripts skip

Review every target action and proposed external source. A successful dry run does not write managed files or LunaPack state. It also does not guarantee that an approved lifecycle script is safe; review scripts separately before changing the mode.

Continue with Discover and install packs when the exact release and preview are acceptable. See Security model and risks for source, script, and managed-file boundaries.