How it works

  1. Build one file

    You build a package with the ael package command, which produces a single package file.

  2. Host it yourself

    You host that file yourself: as a release download in your own GitHub or GitLab project, at any https address, or inside your project.

  3. Pin it in your project

    Your project records the file's address and fingerprint, and AEL refuses the file if it ever changes.

Verified wherever it is hosted

  • AEL verifies every package before using it, whatever its host: its fingerprint, its contents and how it was built.
  • Access tokens for your private host stay outside your project files.

The same rules as official packages

  • Written in AEL

    Every AEL package, from OpenEng or from you, is written in AEL and ships as compiled, verified AEL, with no bundled native code and no install scripts.

  • Never mistaken for an official package

    AEL never treats an external package as an official one, even if its name matches.

  • Never on the official registry

    The official registry never hosts or lists private packages.