Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

If generative AI contributes substantially to code for an open-source project, disclose that use when the project’s rules call for it—and make the extent of the assistance clear. The case for disclosure is about provenance: it gives readers and maintainers useful context about how code was produced. It is Scott Donaldson’s argued position, not a universal rule, and disclosure does not replace a contributor’s responsibility to review the work.

Why disclose substantial AI assistance?

In his September 11, 2026 LinuxLinks essay, Scott Donaldson argues that substantial AI generation is different from routine use of an editor or linter. A tool may produce functions, tests, documentation, refactors, or larger parts of an application. Knowing that history can help users and maintainers understand the project’s provenance and consider its future maintenance.

That reasoning does not mean AI-generated code is inherently bad, nor does disclosure establish that a contribution is defective. It is context about how work was created. Donaldson’s proposed principle is: “If generative AI plays a substantial part in developing an open source project, developers should say so.” Read Donaldson’s essay.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

There is no single disclosure rule for every project

Policies differ in whom they cover, what level of AI use triggers disclosure, where contributors should record it, and what review or licensing checks are expected. Follow the current rules of the project receiving the contribution rather than assuming one foundation’s policy applies everywhere.

Policy Who and what it addresses Disclosure or labeling Other expectations
Linux Foundation Contributions to Linux Foundation projects may include content generated wholly or partly with AI. The cited guidance does not establish a blanket disclosure requirement. Contributors should check that tool terms do not conflict with the project’s open-source license, IP policies, or the Open Source Definition. Linux Foundation guidance.
OpenInfra Foundation Contributors submitting AI-generated or AI-assisted content. Uses “Generated-By” for generative AI contributions and “Assisted-By” for predictive AI assistance; contributors should provide relevant context, including how much came from the tool. Contributors remain responsible for submissions and should review correctness, quality, style, security, and licensing. Project-specific requirements still apply. OpenInfra policy.
pyOpenSci Authors submitting work for its software peer review. Promotes transparency about AI use; the cited policy asks authors to review AI-generated content before submission. Human review helps avoid making volunteer reviewers the first people to find generated errors. pyOpenSci policy.

What a useful disclosure can say

A disclosure should give reviewers enough context to understand the contribution, without implying that a label alone verifies quality. Donaldson offers this example: “Generative AI is used extensively for initial code generation and tests. All generated code is reviewed before merging.” Donaldson’s essay.

Adapt the wording to the project’s required location and terminology. Where the project asks for it, distinguish code generated by a tool from code written by a person with predictive assistance, and describe the scope of that assistance. OpenInfra, for example, specifies Generated-By and Assisted-By labels and asks for context about how much content the tool supplied. OpenInfra’s policy.

Disclosure does not transfer responsibility

A contributor remains accountable for submitted code even when a tool produced some or much of it. Review it for correctness, fit with project style, security issues, and licensing concerns before submission. Also check the terms governing the AI tool against the project’s license and policies; the Linux Foundation’s guidance explicitly raises that compatibility check. Linux Foundation guidance.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

For pyOpenSci submissions, the policy likewise expects authors to review generated material before peer review. pyOpenSci’s review guidance. A disclosure tells others about provenance; it is not a substitute for understanding and checking the contribution.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What the 2026 study says—and does not say

A 2026 study in ACM Transactions on Software Engineering and Methodology combined repository mining with a practitioner survey. It reports 613 mined self-declared AI-generated code snippets and 111 valid survey responses. Among those respondents, 76.6% said they always or sometimes self-declare AI-generated code, while 23.4% said they never do. These figures describe the study’s data and respondents, not developers as a whole. Read the ACM study.

The study describes varied disclosure practices and reported motivations, including tracking use for later review or debugging and ethical considerations. Some respondents who did not disclose said they had substantially modified the generated code or believed declaration was unnecessary. Self-declaration in repositories and surveys is not evidence that undisclosed AI-written code can be reliably detected. Nor does this study establish that disclosure causes better trust, maintainability, or code quality. ACM study.

Best Value
May Open Source Programming Funny DevOps Software Linux Java T-Shirt
  • Open Source, Programmer, Developer, Software Engineer, Code, DevOps, Computer, Software, Scrum, Python, Linux, Stack Overflow, Java, Dotnet, Docker, Terraform, Kubernetes, Deploy
  • Salt, Puppet, Chef, Container, AWS, Azure, Cloud, Coding, Programming, Geek, Funny, Tech, Technical, Compile, Compilation, Science, Bug, Debug
  • Lightweight, Classic fit, Double-needle sleeve and bottom hem

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.