middleapi/orpc

Typesafe APIs Made Simple 🪄

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

Summary Information

Updated 27 minutes ago
Added to GitGenius on September 12th, 2026
Created on September 27th, 2024
Open Issues & Pull Requests: 24 (+0)
GitHub issues: Enabled
Number of forks: 170
Total Stargazers: 5,611 (+0)
Total Subscribers: 13 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.7 hours
Mean response time: 7.3 days
90th percentile: 7.5 days
Tracked items: 308

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 65% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Only 7% of issues opened in the past year have been closed. Three people close 73% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 23
New in 7 days: 0
Closed in 7 days: 9
Avg open age: 280 days
Stale 30+ days: 18
Stale 90+ days: 11

Recent activity

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

Top labels

  • enhancement (102)
  • bug (52)
  • documentation (27)
  • invalid (25)
  • question (17)
  • pending triage (13)
  • upstream (6)
  • good first issue (3)

Most active issues this week

Detailed Description

oRPC is a TypeScript framework for building typesafe APIs with end-to-end type safety across client and server.

The framework solves the problem of maintaining type consistency between API contracts and their implementations across distributed systems. It works by establishing a single source of truth through contract definitions that both server and client code reference. The core approach separates concerns into distinct packages: a contract layer that defines API shapes, a server layer that implements those contracts with middleware and context support, and a client layer that consumes APIs while preserving type information. The framework also provides OpenAPI compatibility, allowing generated or existing OpenAPI specifications to be converted into oRPC contracts.

Teams should adopt oRPC when building TypeScript-based applications where type safety across the API boundary is a priority. It suits projects using modern JavaScript runtimes and frameworks including Node.js, Deno, Bun, Next.js, and Cloudflare Workers, with client-side support for React, Vue, Svelte, and SolidJS. The contract-first approach makes it particularly valuable for teams maintaining multiple client implementations or those integrating with existing OpenAPI-documented services.

The project shows consistent development activity with regular updates across its core packages. The codebase maintains high test coverage and performance monitoring through continuous integration. The maintainers actively engage with the community through a dedicated Discord channel and provide comprehensive documentation covering all major features and use cases.