Open Source Licenses in Robotics Software

Inventory the delivered system

The inventory should identify libraries, operating systems, firmware, development tools, containers, model-related code, and vendor components. It should record versions, licenses, modifications, distribution, and notices. A repository's top-level license may not describe every bundled component.

A component used only in development can present a different issue from code delivered to a customer. A robot image can contain many dependencies that are invisible in the sales interface. Recommended release review should therefore examine the actual delivered artifacts and source obligations, not only the application code written by the team.

Permissions and conditions

Copyright licenses grant permissions subject to their terms. The Copyright Act's exclusive rights and statutory limitations remain relevant. A project should identify what it may copy, modify, distribute, sublicense, or combine and what conditions apply. Open source does not mean absence of ownership. [3]

The analysis should also distinguish copyright permission from patent permission, trademark use, data rights, and support. A software license may contain a patent grant or termination term without granting every right in a dataset, brand, or hardware design. The actual license controls.

GPL version 3

GPL version 3 addresses conveying verbatim and modified source and non-source forms, with conditions and permitted methods. Sections 4 through 6 require careful application to the actual work and distribution. A company should not assume that internal use alone always triggers the same source-delivery obligations as conveying a covered object-code product. [1]

The license also contains patent terms in § 11 and other conditions. Whether combined material forms a covered work is a legal and technical question requiring the actual relationship of components. A universal statement that any contact with GPL software requires disclosure of every company asset is inaccurate, as is a blanket claim that embedding software in hardware avoids the license.

Apache License version 2

Apache version 2 includes copyright and patent grants and redistribution conditions. Section 4 addresses copies, notices of changes, retained notices, and the NOTICE file where applicable. The team should examine the actual source package and modifications rather than generate a generic attribution list unrelated to the delivered version. [2]

The license's patent and termination provisions should be reviewed separately from notices. Its permissions do not establish that third parties have no claims or that the software comes with a commercial support warranty. Vendor support and indemnities require their own agreement.

Distribution, services, and updates

The release process should identify delivery to customers, contractors, resellers, and service providers, and distinguish hosted use from distribution under the actual license. Different licenses can treat network use differently, so the team should not extrapolate GPL terms to every other license.

Updates can introduce new components or obligations. Recommended controls include license review before release, preserved source corresponding to the delivered version where required, notices, offers or delivery methods permitted by the license, and records of compliance. A security patch should not be assumed exempt from licensing conditions merely because it is urgent.

Contracts and procurement

Customer agreements should accurately identify open-source components and the relationship between their licenses and proprietary terms. A proprietary restriction should not purport to remove permissions the distributor is required to preserve. The agreement should also identify support, updates, source access, and responsibility for third-party compliance.

Supplier questionnaires should obtain useful information without treating a declaration of no copyleft as a substitute for review. The relevant questions concern actual components, use, distribution, obligations, and evidence. A software bill of materials can help locate issues but does not itself establish license compliance.

Hypothetical robot release

A Texas vendor ships a robot image containing an operating system, modified utilities, proprietary control software, and an Apache-licensed library. The release review should assess each license and the actual combinations, provide required notices and source arrangements, and preserve the version-specific record. One blanket proprietary notice is not necessarily an adequate treatment of the entire image.