OpenShip’s repository root and GitHub metadata currently identify the project as Apache-2.0. However, apps/email/engine/LICENSE, its README, and source notices identify that component as GPL-3.0.
Could you clarify the intended distribution boundary?
- Is
apps/email/engine intentionally a separately licensed GPL-3.0 component?
- Does a build or distribution of the normal self-hosted OpenShip bundle include or link that engine, or is it an optional separately distributed process?
- Are the remaining root/API/dashboard components intended to remain Apache-2.0 when the email engine is excluded?
- Is there a component-level license inventory that downstream self-hosters should use?
We are evaluating an internal pinned deployment and will keep redistribution of modified OpenShip artifacts blocked until the component obligations are explicit. This question is about the repository’s stated licenses, not a request for legal advice.
OpenShip’s repository root and GitHub metadata currently identify the project as Apache-2.0. However,
apps/email/engine/LICENSE, its README, and source notices identify that component as GPL-3.0.Could you clarify the intended distribution boundary?
apps/email/engineintentionally a separately licensed GPL-3.0 component?We are evaluating an internal pinned deployment and will keep redistribution of modified OpenShip artifacts blocked until the component obligations are explicit. This question is about the repository’s stated licenses, not a request for legal advice.