OpenRewrite recipe distribution shifts from Maven Central to the Code Genome Project

What happened

A story titled "Recipes Are Moving from Maven Central to the Code Genome Project" reached the front page of Hacker News on October 17, 2026. Rather than linking to a blog post or announcement, it points at a page in the OpenRewrite documentation called "Latest versions of every OpenRewrite module" — and that page now carries the most concrete detail accompanying the story: a machine-readable block that installs every OpenRewrite artifact into a system through a GraphQL-style interface.

What the documentation shows

The page's seed script is built as a single GraphQL mutation named seedOpenRewriteArtifacts. Inside it, each OpenRewrite module is loaded through a call to installRecipesUniversal, which takes a bundle described in Maven coordinates: a groupId, an artifactId and a version. In every case the version field is set to "LATEST", meaning resolution happens at install time rather than being pinned in the script.

Two groups of artifacts appear. The first, under the groupId org.openrewrite, covers the framework core and its parsers: rewrite-core, rewrite-java, rewrite-kotlin, rewrite-groovy, rewrite-maven and rewrite-gradle, plus format handlers for JSON, YAML, XML, properties, TOML, HCL, protobuf and Docker files. The second group, under org.openrewrite.recipe, holds the higher-level recipe modules that perform the actual migration work: rewrite-jackson, rewrite-java-dependencies, rewrite-liberty, rewrite-micronaut, rewrite-netty, rewrite-openapi, rewrite-quarkus, rewrite-third-party and the aggregate rewrite-all.

The notable part is not the list itself — a module index is exactly what you would expect on a latest-versions page — but the mechanism wrapped around it. The coordinates are still expressed as Maven artifacts, yet they are consumed through an installRecipesUniversal operation rather than resolved from a repository through ordinary dependency management.

What remains unclear

The linked documentation page does not, on its own, describe a migration. It contains no timeline, no statement about which artifacts will stop publishing to Maven Central, and no definition of what the Code Genome Project actually is. The claim that recipes are moving from Maven Central to the Code Genome Project comes from the Hacker News item's title, not from prose on the page itself.

That gap matters for anyone planning around the change. Questions the available material leaves open include whether existing artifacts will remain available on Maven Central, whether group and artifact identifiers stay stable in the new home, and whether the "LATEST" version policy shown in the seed script reflects how the new system expects recipes to be consumed or is simply a convenience for populating an index.

Why it matters

OpenRewrite is widely used for automated, large-scale refactoring — framework migrations, dependency upgrades and security remediation across whole codebases — and its recipes ship today as ordinary Maven artifacts. If distribution really is moving to a new home, the impact reaches build files, CI pipelines and internal artifact mirrors that currently resolve org.openrewrite and org.openrewrite.recipe coordinates straight from Maven Central.

The seed script also hints at a different consumption model, with recipes fetched and installed through a programmatic interface and version resolution handled elsewhere. For teams that pin exact recipe versions to keep refactors reproducible, how that interface resolves "LATEST" — and whether pinning remains possible — will be the first thing to check once the migration is documented in full.