liveBook · Manning

Open-source laundering

As explained in AI Governance

Open-source laundering is the introduction of open-source code into proprietary software through code copied from an assistant without recognizing its license obligations.

Open-source laundering occurs when code from a coding assistant is copied into proprietary software without recognizing its license obligations. If shipped code is nearly identical to copyleft-licensed code, those obligations may require source disclosure. section 6.6.3

A copied code snippet

A coding assistant suggests a snippet nearly identical to code under GPL or AGPL. A developer pastes it into proprietary software and ships it, potentially triggering copyleft obligations. section 6.6.3

Provider output filters and contractual protections for base-model training data do not cover copyrighted material introduced through retrieval-augmented generation or fine-tuning. section 6.6.3

How AI Governance covers it

How deep it goes
Traces a copied snippet through deployment to possible source-disclosure obligations, but gives no prevention workflow.
Examples
Uses a nearly identical GPL- or AGPL-licensed snippet copied into proprietary software and shipped.
What you can do after
Evaluate whether an assistant-generated snippet may carry copyleft obligations into shipped proprietary code.
How it connects
Connects copyleft licensing with coding assistants, proprietary software, retrieval-augmented generation, and fine-tuning.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of AI Governance. The section links point to the parts of the book it draws on.