Category: AI Governance • Open Source

What it is
Two Oracle-backed projects published opposing AI policies. OpenJDK’s
Governing Board banned contributions generated in whole or part by LLMs or
diffusion models, citing reviewer burden, the JDK’s mission-critical role, and
unresolved IP ownership of AI output under its Contributor Agreement. Editing
even 10 of 100 AI-generated lines still counts as AI-generated. GraalVM, by
contrast, permits AI coding assistants, placing full accountability on the human
contributor to explain, defend, and maintain any AI-assisted change. Both
projects use the same contributor agreement.
Why it Matters for Enterprises
Even within one company, AI-contribution policy varies by project risk profile.
Enterprises contributing to or relying on open-source Java tooling should check
each project's AI policy individually - and apply the same contributor
accountability standard internally for AI-assisted code.