|  | 
|  | 1 | +--- | 
|  | 2 | +layout: post | 
|  | 3 | +title: "Announcing Elixir OpenChain Certification" | 
|  | 4 | +authors: | 
|  | 5 | +  - Jonatan Männchen | 
|  | 6 | +  - José Valim | 
|  | 7 | +category: Announcements | 
|  | 8 | +excerpt: "The Elixir project now meets OpenChain (ISO/IEC 5230). Each release ships with Source SBoMs in CycloneDX 1.6 and SPDX 2.3, plus attestation." | 
|  | 9 | +tags: openchain compliance | 
|  | 10 | +--- | 
|  | 11 | + | 
|  | 12 | +We are pleased to share that the Elixir project now complies with | 
|  | 13 | +[OpenChain][openchain] ([ISO/IEC 5230][iso_5230]), an international | 
|  | 14 | +standard for open source license compliance. This step aligns with broader | 
|  | 15 | +efforts to meet industry standards for supply chain and cybersecurity best | 
|  | 16 | +practices. | 
|  | 17 | + | 
|  | 18 | +## Why OpenChain Compliance Helps | 
|  | 19 | + | 
|  | 20 | +By following OpenChain, we demonstrate clear processes around license | 
|  | 21 | +compliance. This benefits commercial and community users alike, making Elixir | 
|  | 22 | +easier to adopt and integrate with confidence. | 
|  | 23 | + | 
|  | 24 | +## Changes for Elixir Users | 
|  | 25 | + | 
|  | 26 | +- All future Elixir releases will include a Source SBoM in | 
|  | 27 | +  [CycloneDX 1.6 or later][cyclonedx] and [SPDX 2.3 or later][spdx] formats. | 
|  | 28 | +- Each release will be attested along with the Source SBoM. | 
|  | 29 | + | 
|  | 30 | +These additions offer greater transparency into the components and licenses of | 
|  | 31 | +each release, supporting more rigorous supply chain requirements. | 
|  | 32 | + | 
|  | 33 | +## Changes for Contributors | 
|  | 34 | + | 
|  | 35 | +- Contributions remain under the Apache-2.0 License. Other licenses cannot be | 
|  | 36 | +  accepted. | 
|  | 37 | +- The project now enforces the [Developer Certificate of Origin (DCO)][dco], | 
|  | 38 | +  ensuring clarity around contribution ownership. | 
|  | 39 | + | 
|  | 40 | +Contributors will notice minimal procedural changes, as standard practices | 
|  | 41 | +around licensing remain in place. | 
|  | 42 | + | 
|  | 43 | +For more details, see the [CONTRIBUTING guidelines][contributing]. | 
|  | 44 | + | 
|  | 45 | +## Commitment | 
|  | 46 | + | 
|  | 47 | +These updates were made in collaboration with the | 
|  | 48 | +[Erlang Ecosystem Foundation][erlef], reflecting a shared | 
|  | 49 | +commitment to robust compliance and secure development practices. Thank you to | 
|  | 50 | +everyone who supported this milestone. We appreciate the community’s ongoing | 
|  | 51 | +contributions and look forward to continuing the growth of Elixir under these | 
|  | 52 | +established guidelines. | 
|  | 53 | + | 
|  | 54 | +[openchain]: https://openchainproject.org/ | 
|  | 55 | +[erlef]: https://erlef.org/ | 
|  | 56 | +[spdx]: https://spdx.org/rdf/terms/ | 
|  | 57 | +[cyclonedx]: https://cyclonedx.org/specification/overview/ | 
|  | 58 | +[iso_5230]: https://www.iso.org/standard/81039.html | 
|  | 59 | +[dco]: https://developercertificate.org/ | 
|  | 60 | +[contributing]: https://github.com/elixir-lang/elixir/blob/main/CONTRIBUTING.md | 
0 commit comments