Code Generation

oapi-codegen8.4k★

oapi-codegen turns OpenAPI 3.0 specs into Go code. Generate server boilerplate for Chi, Echo, Fiber, Gin, gorilla/mux, Iris, or net/http; generate API clients with custom request editors; or just generate types from your schemas. Apache 2.0, free, idiomatic Go output. No service to run; it's a code generator you invoke from your build. The strict server mode handles request and response marshaling automatically. Recent versions added import mapping so you can split a giant spec across packages, which actually matters when your API surface gets big. This is the standard for OpenAPI-first Go services. If you have a spec, you should be using this. Solo, small, large, all the same answer: free, run it as part of your codegen pipeline, save yourself days of boilerplate. The catch: OpenAPI 3.1 support is experimental, the release cadence is loose (pinning to commits is recommended for unreleased features), and the generated code aims for simplicity over refactoring, so you'll see some duplication. Implicit additionalProperties are also ignored by default. Read the docs before you assume your spec round-trips perfectly.

rewrite3.6k★

OpenRewrite automates the most tedious job in software maintenance: updating old code. Migrating to a new framework version, swapping out a dead library, patching a known security hole, normally that's a developer grinding through files by hand. OpenRewrite does it for you. You pick a "recipe" (a pre-written set of instructions for a specific change), point it at your codebase, and it rewrites the files while preserving your original formatting, so the diff is reviewable instead of a mess. The engine is Apache 2.0 and free, built by a company called Moderne. What makes it more reliable than find-and-replace is that it actually understands your code. It parses everything into a type-aware tree, so changes are context-aware, not blind text substitution. You run recipes through first-class Maven and Gradle plugins. Java is by far the deepest and most mature target; Kotlin, JavaScript and TypeScript, Python, and C# are supported but less complete. Running a recipe against a single repository is entirely free and needs no account. The work on your end is picking the right recipe, configuring it, running it, and reviewing what it produced, plus a learning curve if you want to author your own recipes. The paid layer, Moderne's platform, is about scale: running recipes across hundreds or thousands of repositories at once, with impact analysis and dashboards on top. So the honest split is that the thing that does the refactoring is free, and what you pay for is doing it across an entire organization's fleet with governance. Solo developers and small teams on a handful of repos: the free engine is all you need. Large teams drowning in multi-repo migrations are exactly who Moderne's commercial product targets. The catch is the gravity toward the paid tier. Single-repo, the free version is genuinely complete. But the moment your problem is organization-wide, the manual multi-repo workflow gets painful fast, which is by design. If you're mostly a Java shop with migration debt, this is a clear win. Outside Java, check that the recipes you need actually exist before counting on it.