getkin/kin-openapi

OpenAPI 3.0 and 3.1 and 3.2 (and Swagger v2) implementation for Go (parsing, converting, validation, and more)

View on GitHub ↗Jump to charts ↓Open shareable report →

getkin/kin-openapi has 3k+ stars and 500+ forks on GitHub, is written in Go, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Library / SDKCategory(s):API Development ToolsDeveloper Tools
Added to GitGenius on September 21st, 2026
Created on June 11th, 2017
Open Issues & Pull Requests: 84 (+0)
GitHub issues: Enabled
Number of forks: 528
Total Stargazers: 3,305 (+0)
Total Subscribers: 18 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.9 days
Mean response time: 152.7 days
90th percentile: 449.8 days
Tracked items: 108

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 3
Closed in 7 days: 11
Avg open age: 488 days
Stale 30+ days: 16
Stale 90+ days: 13

Recent activity

Opened in 7 days: 2
Closed in 7 days: 5
Comments in 7 days: 0
Events in 7 days: 4

Top labels

  • OpenAPI3.1 (1)
  • enhancement (1)
  • help wanted (1)
  • openapi3filter (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

kin-openapi is a Go library that implements OpenAPI 3.0, 3.1, and 3.2 specifications along with Swagger v2 support, providing parsing, conversion, validation, and related functionality.

The library addresses the need to work programmatically with OpenAPI specifications in Go applications. It handles the full lifecycle of OpenAPI documents: reading and parsing specification files, converting between different OpenAPI versions, validating documents against their schema, and performing other operations on specification data. This allows developers to build tools, servers, and clients that understand and manipulate API specifications as structured data rather than treating them as static documentation.

The tool suits projects that need to integrate OpenAPI specifications into their build or runtime workflows. This includes API servers that want to validate incoming requests against their OpenAPI definition, code generators that consume specifications, API documentation tools, and testing frameworks. Teams working with multiple OpenAPI versions will appreciate the broad version support, which eliminates the need to maintain separate parsing logic for different specification formats. The library is particularly valuable for Go-based infrastructure and tooling where OpenAPI specifications are a first-class concern rather than an afterthought.

The project maintains active engagement with contributions and issue resolution. Pull requests receive timely review and feedback from maintainers. The codebase shows consistent attention to both new feature requests and bug reports, with maintainers providing detailed responses that guide contributors toward solutions. The project demonstrates responsiveness to community needs while maintaining standards for code quality and specification compliance.