graphql-python

graphene: Build GraphQL APIs in Python

Graphene is a Python library for defining GraphQL schemas and resolving queries against your application’s data. It supports Relay and works with different data sources, but its recent inactivity is an important adoption risk.

InactivePythonMITFrameworkLibraryGraphQL
View on GitHub Compare
Stars
8.2k
Forks
823
Stars, last 30 days
+2
Last commit
1.1 years ago
Contributors
100+

Our take

Inactiveno commits in over a year

Health score

33/100

How it is scored
Activity
19
Community
70
Issues
21
Pull requests
20

+2 stars in the last 30 days

  • More contributors than 78% of the projects we track

Graphene provides a flexible, MIT-licensed foundation for Python GraphQL APIs, but its lack of recent development makes it a higher-maintenance choice for new production systems.

Good fit if

  • You need a Python GraphQL schema and can evaluate whether the existing project meets your needs.
  • Relay support or data-source flexibility is useful to your application.
  • You can maintain or adapt the library if development remains inactive.

Look elsewhere if

  • You need an actively maintained framework, since there have been no commits in over a year and no release in the past year.
  • Your adoption depends on upstream issue or pull request turnaround, with no issues closed or pull requests merged in the recent measurement period.
All health signals
Last commit2025-09-04 (1.1 years ago)
Commits, last 90 days0
Releases, last 12 months0 (latest v3.4.3, 2024-11-09)
Contributors100+ (top contributor: 69% of commits)
Issues closed, last 90 days0
Pull requests merged, last 90 days0
Project age11 years

Checked on 2026-10-12 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

8,240

Forks

824

Change since Nov 16, 2026: 0 stars·-1 forks

Overview

Graphene is a Python framework for building GraphQL schemas and APIs. You define schema types in Python and write resolvers that connect GraphQL queries to your application’s data, rather than tying the schema to a particular database or storage system.

It suits Python teams that want to expose data through GraphQL, including teams using Relay. Framework-specific integrations such as Django and SQLAlchemy are separate packages.

Key Features

  • Define GraphQL object types, fields, and schemas in Python.
  • Resolve queries using application logic and data from different sources.
  • Execute GraphQL queries through the schema API.
  • Built-in support for Relay patterns.
  • Integrations are available for Django, SQLAlchemy, MongoDB, and Apollo Federation through related packages.
  • Compatible with GraphQL clients including Relay, Apollo Client, and gql.

Use Cases

  • A Python backend team can expose application data through a GraphQL API when clients need to request specific fields.
  • A team using Relay can build a Python GraphQL schema with the framework’s Relay support.
  • A Django or SQLAlchemy project can pair Graphene with the corresponding integration package to connect its existing data layer.
  • An application with data spread across custom Python objects or different storage systems can use resolvers to bring that data together behind a GraphQL schema.

What you need

Detected in the repository

  • Python (from setup.py)
  • Automated checks on GitHub Actions

License in plain words

MITpermissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the copyright and license notice
  • Share your changes: no

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Install Graphene with pip:

pip install "graphene>=3.1"

See the README and the project documentation for schema examples, integrations, and contribution details.

Considerations

The project is marked inactive: it has had no commits in over a year and no release in the past year. While the contributor base is broad and contributions are not concentrated in one person, recent issue and pull request activity indicates limited visible maintenance. The README describes testing and compatibility workflows, but teams should independently verify the maintenance and compatibility they require before adopting it. Django, SQLAlchemy, MongoDB, and Apollo Federation support comes through separate integration packages, not the core library.

Found this useful?

Share it with someone who would like graphene.