fern-api/fern

Input OpenAPI. Output SDKs and Docs.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 18th, 2026
Created on April 1st, 2022
Open Issues & Pull Requests: 334 (+0)
GitHub issues: Enabled
Number of forks: 346
Total Stargazers: 3,783 (+0)
Total Subscribers: 17 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.0 days
Mean response time: 101.7 days
90th percentile: 367.2 days
Tracked items: 670

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 94% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "errors" is answered fastest, typically in under an hour, while "configuration" waits about 10 days. 42% of tracked open issues have had no activity in three months. Only 43% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 245
New in 7 days: 3
Closed in 7 days: 7
Avg open age: 303 days
Stale 30+ days: 108
Stale 90+ days: 71

Recent activity

Opened in 7 days: 3
Closed in 7 days: 6
Comments in 7 days: 6
Events in 7 days: 10

Top labels

  • product/docs (185)
  • Stale (173)
  • product/sdk-generator (87)
  • documentation (49)
  • component:docs (42)
  • product/CLI (35)
  • configuration (30)
  • priority:p1-high (28)

Detailed Description

Fern is a code generation platform that transforms API definitions into production-ready SDKs and documentation.

Fern solves the problem of maintaining multiple SDKs and API documentation in sync with your API specification. It takes OpenAPI, AsyncAPI, Protobuf, or OpenRPC definitions as input and generates type-safe SDKs in TypeScript, Python, Java, Go, Ruby, PHP, and C#, along with interactive developer documentation. The approach is specification-driven: you define your API once, and Fern generates all downstream artifacts automatically, eliminating manual synchronization work.

Teams should adopt Fern if they maintain APIs and want to reduce the effort of SDK generation and documentation maintenance across multiple languages. It suits projects where consistency across SDKs matters and where you want to ship documentation alongside code. The tool includes built-in features like interactive API reference generation, markdown-based additional pages with git versioning, search functionality, dark mode, and customizable branding. The platform also offers AI-powered search trained on your documentation, APIs, and SDKs to answer developer questions automatically.

The project maintains active development with regular updates to its SDK generators and documentation features. The codebase shows consistent refinement of the code generation pipeline and expansion of supported API specification formats. Development activity indicates ongoing investment in both the core generation engine and the ecosystem of available generators that users can add to their workflows.