middleapi/orpc

Typesafe APIs Made Simple 🪄

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

middleapi/orpc has 5.5k+ stars and 150+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 12th, 2026
Created on September 27th, 2024
Open Issues & Pull Requests: 28 (+0)
GitHub issues: Enabled
Number of forks: 172
Total Stargazers: 5,690 (+1)
Total Subscribers: 12 (+0)

Repository Insights (GitGenius)

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

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 4% of issues opened in the past year have never received a reply. 65% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. 88% of issues opened in the past year have been closed, leaving a working backlog. Three people close 74% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 23
New in 7 days: 1
Closed in 7 days: 3
Avg open age: 261 days
Stale 30+ days: 19
Stale 90+ days: 14

Recent activity

Opened in 7 days: 1
Closed in 7 days: 3
Comments in 7 days: 2
Events in 7 days: 5

Top labels

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

Most active issues this week

Sign in to see which issues are moving.
Sign in

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.