// the take
PhoenixSwagger generates a Swagger 2.0 spec straight from your Phoenix router and controller annotations, serves Swagger UI, and gives you plugs/test helpers to validate requests and responses against that spec. It's for Elixir/Phoenix teams who want API docs that can't silently drift too far from the actual endpoints, without hand-writing a spec file by hand.
The compile-time mix task (compile.phoenix_swagger) regenerates the spec as part of your build, so it's not a manual 'remember to run this' step. Request validation via ConnValidator and response schema validation in ExUnit tests are the real selling point — you can assert a controller's JSON actually matches the documented schema instead of trusting the annotations. Bundling swagger-ui directly in priv/static means you get a working docs UI with zero extra JS tooling or separate deploy.
It only speaks Swagger 2.0, not OpenAPI 3.x — if you need OAS3 features (oneOf/anyOf, better auth scheme modeling, newer codegen tooling) you're out of luck. Documentation lives in swagger_path/swagger_definitions macros scattered across controllers, which is a lot of DSL to hand-write and easy to let rot since nothing forces every action to have a schema — only the ones you bother to annotate get validated. It's effectively a single-org-maintained project (xerions) with a slow release cadence, so if Phoenix or the Swagger/OpenAPI ecosystem moves, you may be waiting a while for compatibility fixes.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →