Skip to content

Package Safety Gate

ImperaZim edited this page Jun 28, 2026 · 1 revision

Package Safety Gate

The Package Safety Gate prevents invalid local package state from arming a package-backed PMMP proxy.

Package-backed proxies are real PMMP plugin identities. If a generated proxy has an active plugin.yml, PMMP can discover it on the next boot. The safety gate makes EasyLibrary stop before that boundary when the package is not safe.

Checks

The gate checks:

  • package state identity, version and path;
  • installed package.yml and Package Contract v1 validity;
  • manifest/catalog drift;
  • required package dependencies;
  • PSR-4 autoload folders;
  • malformed sha256 metadata;
  • package-lock.yml drift.

State

When blocked, package doctor reports:

safe-blocked

This means the package may exist on disk, but EasyLibrary will not arm the generated proxy until the listed problems are fixed.

Commands

/easylibrary packages doctor
/easylibrary packages proxies doctor <package>
/easylibrary packages repair <package>
/easylibrary packages repair <package> confirm

repair confirm can park an unsafe proxy marker and fix conservative metadata, but it does not recreate damaged package files. Use install/update or rollback when the installed package itself is broken.

Recovery Shape

/easylibrary packages repair libform confirm
/easylibrary packages doctor
/easylibrary packages proxies doctor libform
elprobe run libform

If the package remains safe-blocked, read the listed reason. Common causes are a missing package.yml, missing required package dependency, broken autoload path or lock/state version drift.

Clone this wiki locally