ruby-grape/grape

An opinionated framework for creating REST-like APIs in Ruby.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 28 minutes ago
Added to GitGenius on September 6th, 2026
Created on August 2nd, 2010
Open Issues & Pull Requests: 236 (+0)
GitHub issues: Enabled
Number of forks: 1,231
Total Stargazers: 10,003 (+0)
Total Subscribers: 194 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.0 hours
Mean response time: 79.8 days
90th percentile: 327.6 days
Tracked items: 71

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 6% of issues opened in the past year have been closed. Three people close 85% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 10
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,458 days
Stale 30+ days: 10
Stale 90+ days: 8

Recent activity

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

Top labels

  • bug? (24)
  • confirmed bug (9)
  • feature request (9)
  • chore (4)
  • discuss! (4)
  • needs info (4)
  • question (4)
  • you can help (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Grape is a REST-like API framework for Ruby that runs on Rack or integrates with existing web frameworks like Rails and Sinatra.

Grape solves the problem of building RESTful APIs in Ruby by providing a simple domain-specific language for API development. It handles common API concerns through built-in conventions including multiple response formats, content negotiation, API versioning, subdomain and prefix restrictions, and automatic HEAD and OPTIONS route generation. The framework works as a Rack application that can be mounted standalone or alongside other frameworks, with routes compiled either on first access or pre-loaded for performance.

Grape suits teams building APIs in Ruby who want to avoid boilerplate while maintaining control over API design. It works well as a dedicated API layer in Rails applications or as a standalone service. The framework is particularly useful when you need versioning, multiple content formats, or fine-grained control over request and response handling without the overhead of a full web framework. Developers should note that Ruby 3.3 or newer is required.

The project maintains active engagement with its community through issue tracking and social media presence. Commercial support and maintenance are available through a subscription service. The framework includes integration with Rails deprecation systems, allowing applications to manage Grape deprecations through their standard Rails configuration. The codebase supports pre-compilation of routes to optimize startup performance in production environments.