GoKawiilOpenRewrite shifts module distribution from Maven Central to Code Genome Project
OpenRewrite is now distributing its modules through the Code Genome Project rather than Maven Central, requiring developers to add a new repository and authentication credentials to their builds. Maven Central remains necessary for resolving OpenRewrite's transitive dependencies, and a bill of materials artifact is published with each release to align module versions. The Gradle plugin is also now hosted on the Code Genome Project instead of the Gradle Plugin Portal.
GoKawiil's interpretation of the reporting above, not reported fact.
The move adds an authentication requirement for a widely used code-refactoring tool, meaning teams must obtain tokens and update build configurations or risk broken dependency resolution. Organizations that mirror repositories internally via Artifactory or Nexus can sidestep direct credential management, which could ease adoption for larger engineering teams. The split between Maven Central and a separate authenticated registry suggests OpenRewrite's maintainers are seeking more control over distribution, though the source does not state their reasoning.
- OpenRewrite modules now require authentication via the Code Genome Project rather than open access through Maven Central.
- Maven Central is still needed for transitive dependencies, so both repositories must be configured together.
- The Gradle plugin has also moved off the Gradle Plugin Portal and onto the Code Genome Project.
Source: docs.openrewrite.org, 2026-10-15
Published there as: “Recipes Are Moving from Maven Central to the Code Genome Project”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.