How it will work

  1. Build one file

    With the beta, you will build a package with the ael package command (command names may change before launch), which will produce a single package file.

  2. Host it yourself

    You will 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 will record the file's address and fingerprint, and AEL will refuse the file if it ever changes.

Verified wherever it is hosted

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

The same rules as official packages

  • Written in AEL

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

  • Never mistaken for an official package

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

  • Never on the official registry

    The official registry will never host or list private packages.