Apply the commercial-activity condition
The exclusion is not a blanket rule that all open-source software falls outside product liability. Identify who developed or supplied the software, the commercial setting and how the affected product uses it. A commercial product can contain open-source components, and the finished-product manufacturer has its own role. Avoid assigning a legal outcome solely from the licence name.
Separate the project and the integration
An upstream project, a commercial distributor and a device manufacturer may perform different activities. Record the software version, changes made by integrators and who authorised its supply or interconnection. A free download does not by itself establish that every supply activity is non-commercial, while commercial use of a component does not justify an automatic liability conclusion about every upstream contributor.
Preserve the relevant history
Keep the licence, project provenance, release artefact, commercial supply arrangements and integration records. These can help explain the scope and actor questions. The actual compensation analysis still needs defectiveness, covered damage and causation, together with the applicable law and any relevant exemption.
Records that help the review
Use the following as a practical starting point. Select and preserve records appropriate to the product, incident and applicable procedure.
- Licence and software provenance
- Commercial development or supply arrangements
- Integration approvals and affected versions
- Changes made by distributors or integrators
Open source is not a synonym for automatic exemption, and commercial integration does not establish that every contributor is liable.
Primary sources and legal scope
This page explains the EU Directive framework. Check national implementing law, the corrected temporal scope and relevant procedure before applying it to a case.
- Directive (EU) 2024/2853, consolidated text: Articles 2, 4, 8 ↗
- Official Journal corrigendum, 7 May 2026: Article 2(1) ↗
Source register: corrected scope verified 16 October 2026. Article references identify the legal basis. No qualified legal review or national implementation status is claimed.