# Component licenses and packaging This inventory describes the license notices and packaging scripts in this checkout. It does not change any license or replace a component's own notices. The root package's Apache-2.0 metadata is not a license for every file included in a distribution. | Component | Recorded license and provenance | | --- | --- | | Openship-authored root, API, dashboard, CLI and desktop code | [Apache License 2.0](../LICENSE); their package metadata also declares Apache-2.0. Third-party code and dependencies retain their own terms. | | `apps/email/engine` | Vendored iRedMail, with its [GPL v3 license text](../apps/email/engine/LICENSE), [upstream README](../apps/email/engine/README.md), and file-level notices. For example, [iRedMail.sh](../apps/email/engine/iRedMail.sh) grants GPL version 3 or any later version. Preserve the applicable file notices. | | `apps/email/client` and `apps/email/server` | The [email package](../apps/email/package.json) identifies these as Zero Email. This checkout has no separate license file or `license` field for those subpackages. Their upstream revision and required notices still need a provenance review; this inventory does not assign them the root license. | | Package dependencies, base images and installed mail daemons | Their upstream licenses apply independently. This table is a repository-component inventory, not a complete inventory of transitive dependencies or OS packages. | ## Where the engine is included Mail execution is optional, but the engine source is already included in these distribution recipes: | Distribution | Included path | Packaging source | | --- | --- | --- | | API container image | `/app/apps/email/engine` | [API Dockerfile](../apps/api/Dockerfile) copies the engine tree into the final image. | | CLI package and staged CLI payload | `dist/server/engine` | [Server staging](../apps/cli/build/stage-server.ts) copies the engine, including its license and notices; [payload staging](../apps/cli/build/stage-cli-payload.ts) copies that distribution. | | Packaged desktop app | `resources/engine` | [Desktop staging](../apps/desktop/build/stage.ts) copies the engine tree. | | Mail engine container image | `/opt/iRedMail-engine` | [Mail Dockerfile](../apps/email/Dockerfile) copies the engine and runs its installer during the image build. | | Source checkout/archive | `apps/email/engine` | The vendored tree is part of this repository. | These staging steps copy the shell installer and configuration sources as files; they do not compile them into the TypeScript API. Mail runs as separate daemons managed through the mail setup/runtime integration. That process boundary does not remove the engine from a package that includes its files. The standalone source API release generated by [build-release.ts](../apps/api/scripts/build-release.ts) copies the API, dashboard and selected workspace packages; its recipe does not copy the engine tree. The standalone webmail release generated by [the email build script](../apps/email/scripts/build-release.ts) copies the Zero client/server, not the iRedMail engine. Those are different artifacts from the API and mail Docker images above. Excluding the engine does not change the declared Apache-2.0 license of Openship-authored code. It also does not change the licenses of other included third-party code. Preserve the engine's source, license text and notices when packaging it, and assess a pinned artifact using what it actually contains. ## Remaining inventory work The Zero Email provenance and missing component notices are not resolved by documenting the iRedMail boundary. Track that review in [#610](https://github.com/oblien/openship/issues/610). A complete distribution inventory also needs the versions and licenses of its dependency and OS-package closure; the root Apache-2.0 badge alone cannot supply that information.