pyeve/eve

REST API framework designed for human beings

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 38 minutes ago
Added to GitGenius on September 9th, 2026
Created on October 22nd, 2012
Open Issues & Pull Requests: 29 (+0)
GitHub issues: Enabled
Number of forks: 740
Total Stargazers: 6,747 (+0)
Total Subscribers: 216 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.9 hours
Mean response time: 12.3 hours
90th percentile: 33.2 hours
Tracked items: 5

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 538 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Eve is a REST API framework that allows developers to build and deploy customizable RESTful web services with minimal configuration.

Eve solves the problem of rapid API development by providing a batteries-included framework that handles common REST patterns out of the box. The framework takes a configuration-driven approach, requiring only a database connection, a settings file, and a launch script to bring an API online. It emphasizes simplicity in setup while offering extensive customization options for more complex requirements. The tool is built on Flask and provides native MongoDB support alongside SQL backends through community extensions.

Eve suits teams building internal APIs, microservices, or data-driven applications where time-to-deployment matters. It works well for projects that need standard REST operations without extensive custom logic. The framework's read-only-by-default stance and built-in support for authentication, rate limiting, and data validation make it appropriate for production APIs. Developers should choose Eve if they value configuration over code and want to avoid boilerplate; it is less suitable for APIs requiring highly specialized request handling or those already committed to a different web framework ecosystem.

The project maintains active continuous integration workflows. Development follows a code style standard enforced through automated tooling. The framework receives ongoing maintenance and accepts community contributions to extend its capabilities, particularly through SQL backend support developed outside the core project.