swaggo/gin-swagger

gin middleware to automatically generate RESTful API documentation with Swagger 2.0.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 49 minutes ago
Added to GitGenius on September 16th, 2026
Created on June 22nd, 2017
Open Issues & Pull Requests: 111 (+0)
GitHub issues: Enabled
Number of forks: 297
Total Stargazers: 4,238 (+0)
Total Subscribers: 38 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 38.8 days
Mean response time: 122.6 days
90th percentile: 397.3 days
Tracked items: 21

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 20
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,149 days
Stale 30+ days: 20
Stale 90+ days: 20

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

gin-swagger is a middleware for the Gin web framework that automatically generates RESTful API documentation in Swagger 2.0 format.

The tool solves the problem of maintaining API documentation in sync with code changes. It works by parsing Go source code annotations in your handler functions and automatically generating Swagger specification files and interactive documentation. Developers annotate their route handlers with structured comments describing parameters, responses, and other metadata, and the middleware generates the corresponding OpenAPI documentation without requiring manual specification files.

The project suits Go developers building REST APIs with Gin who want to reduce the overhead of maintaining separate API documentation. It is particularly valuable for teams that want documentation to stay current as the API evolves, since the source of truth remains in the code itself. This approach eliminates the friction of keeping a separate Swagger file synchronized with implementation changes.

The project shows consistent maintenance with regular updates addressing issues and adding features. Pull requests receive timely review and feedback from maintainers. The codebase demonstrates active engagement with the community through issue resolution and incorporation of user-requested improvements. Development activity indicates a stable project that responds to reported problems and evolving requirements in the Gin ecosystem.