keystonejs/keystone

The superpowered headless CMS for Node.js — built with GraphQL and React

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 6th, 2026
Created on April 5th, 2018
Open Issues & Pull Requests: 137 (+0)
GitHub issues: Enabled
Number of forks: 1,261
Total Stargazers: 9,970 (+0)
Total Subscribers: 79 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 32.7 hours
Mean response time: 54.0 days
90th percentile: 113.0 days
Tracked items: 200

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 86% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 7% of issues opened in the past year have been closed. Three people close 83% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 56
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,082 days
Stale 30+ days: 56
Stale 90+ days: 53

Recent activity

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

Top labels

  • help wanted (13)
  • dependencies (10)
  • needs more info (5)
  • discussion (3)
  • documentation (3)
  • needs reproduction (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Keystone is a headless CMS framework for Node.js that provides a GraphQL API and an admin interface built with React.

The tool addresses the need for a developer-friendly content management system by combining a GraphQL server with a React-based admin UI. It allows developers to define content models through code, which automatically generates both the GraphQL API and the corresponding admin interface for managing that content. This approach eliminates the need to build these components separately and keeps the content model definition in a single place.

Keystone suits teams building content-driven applications who want to avoid the overhead of building custom admin interfaces or adopting a traditional CMS with limited customization. It works well for projects where developers want to maintain control over their content structure and API while still providing non-technical users with an intuitive interface for content management. The tool is particularly valuable for teams already comfortable with Node.js, GraphQL, and React, as these technologies form its foundation.

The project maintains active development with regular updates to its core packages and documentation. The maintainers respond to community issues and pull requests, indicating ongoing engagement with users. The codebase shows consistent refinement of features and bug fixes across releases. Community channels including Slack and social media are actively monitored, suggesting the team prioritizes developer support and feedback.