swagger-api/swagger-core

Examples and server integrations for generating the Swagger API Specification, which enables easy access to your REST API

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 5 minutes ago
Added to GitGenius on September 8th, 2026
Created on July 5th, 2011
Open Issues & Pull Requests: 197 (+0)
GitHub issues: Enabled
Number of forks: 2,259
Total Stargazers: 7,531 (+0)
Total Subscribers: 308 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 190.7 days
Mean response time: 949.5 days
90th percentile: 2771.3 days
Tracked items: 844

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "Question" is answered fastest, typically in about 3 days, while "backlog" waits about 4 weeks. Only 2% of issues opened in the past year have been closed. Three people close 89% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 154
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 873 days
Stale 30+ days: 136
Stale 90+ days: 130

Recent activity

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

Top labels

  • backlog (197)
  • Bug (65)
  • Feature (18)
  • Question (10)
  • P2 (6)
  • P3 (5)
  • pull-request-welcome (4)
  • P1 (2)

Detailed Description

Swagger Core is a Java implementation of the OpenAPI Specification that generates API documentation from your REST API code.

The tool solves the problem of keeping API documentation in sync with implementation by automatically generating OpenAPI specification documents from annotated Java code. It works by scanning JAX-RS2 endpoints and their annotations, extracting metadata about request and response structures, and producing machine-readable specifications that describe your REST API.

Developers should choose this tool if they are building REST APIs in Java using JAX-RS2 and want to maintain accurate, up-to-date API documentation without manual effort. It suits projects where the API contract needs to be discoverable by client developers and tooling. The tool supports both the javax and jakarta namespaces, allowing use in projects that have migrated to Jakarta EE. It also supports OpenAPI 3.1 in addition to earlier specification versions, giving teams flexibility in which OpenAPI version they target.

The project maintains active build and deployment workflows, with continuous integration testing across the codebase. Documentation is centralized in the project wiki, which contains getting started guides, samples, and contribution guidelines. The project acknowledges multiple specification versions and provides clear migration paths, including a separate branch for users who need the older 1.5.X line with OpenAPI 2.0 support.