swag
Automatically generate RESTful API documentation with Swagger 2.0 for Go. observed · 2026-08-28
Health v2 · maintenance only
78/100
- Activity 98
- Release rhythm 41
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 103.0
- age_days: 3371
- days_rel: 236
- days_push: 15
- n_releases_24m: 5
Adoption not part of the score
12994 stars · 1550 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Swag converts Go source code annotations into Swagger 2.0 (OpenAPI) documentation, with a CLI generator and integrations for popular Go web frameworks like Gin. It lets developers keep API docs alongside their handlers and serve them via Swagger UI.
Use cases
- generate swagger docs from go comments
- document a gin rest api
- serve swagger ui for a go backend
- auto-generate openapi spec for go project
- keep api documentation in sync with code
- add swagger annotations to go handlers
When to choose
- you write Go web APIs and want docs generated from code comments
- you use Gin, Echo, or other supported Go frameworks and want Swagger UI integration
- you want OpenAPI/Swagger 2.0 specs without hand-writing YAML
When to avoid
- you need OpenAPI 3.x support specifically
- your API is not written in Go
- you prefer spec-first (design-first) workflows writing OpenAPI by hand
Facets
cli-tool · maturity stable
api-documentation documentation cli developer-tools developer-tools apis documentation web-development go cli cross-platform swagger openapi swagger-ui gin code-generation annotations rest-api
1 source
- readme: https://github.com/swaggo/swag · fetched 2026-08-28 · 9c4625551d9c
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| swaggo/swag | main | 78 |
| swaggo/gin-swagger | plugin | 66 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem