Most net stars, last 30 days
dosco/graphjinOne governed graph for AI agents — GraphQL + MCP over your databases, files, APIs, and code
+65
25% of the net stars of this Tag
Tags / Backend and APIs /
GraphQL server
A library or server that serves a GraphQL API.
The 40repositories with this Tag gained +261 net stars in the last 30 days, 8% more than the 30 days before.
0 created in the last 90 days · 23 published a release in the last 30 days · 245K stars in total
Oct 5, 2026Nov 3, 2026
- Seed Dataset
- Rising Admissions
Largest Pace, last 30 days
No other repository gained 2 or more times the net stars of the 30 days before.
Most stars, created in the last 90 days
No other repository with this Tag was created in the last 90 days.
Where the stars went, last 13 weeks
Net stars gained each week. The repositories that gained the most have their own color.
hasura/graphql-engine gained 16% of the net stars of this Tag in the last 13 weeks.
- hasura/graphql-engine16%
- dosco/graphjin14%
- ChilliCream/graphql-platform6%
- 99designs/gqlgen6%
- strawberry-graphql/strawberry5%
- All other repositories53%
Compare growth
40 repositories with this Tag. Select a column name to change the order.
| # | Repository | Stars | Gained, 30 days | Pace | |
|---|---|---|---|---|---|
| 21 | nuwave/lighthouse A framework for serving GraphQL from Laravel | 3.5K | +4 | – | |
| 22 | graphql-nexus/nexus Code-First, Type-Safe, GraphQL Schema Construction | 3.4K | +4 | – | |
| 23 | mercurius-js/mercurius Implement GraphQL servers and gateways with Fastify | 2.5K | +4 | – | |
| 24 | graphql-python/graphene GraphQL framework for Python | 8.2K | +3 | – | |
| 25 | absinthe-graphql/absinthe The GraphQL toolkit for Elixir | 4.4K | +3 | – | |
| 26 | rmosolgo/graphql-ruby Ruby implementation of GraphQL | 5.4K | +2 | – | |
| 27 | graph-gophers/graphql-go GraphQL server with a focus on ease of use | 4.8K | +2 | – | |
| 28 | sangria-graphql/sangria Scala GraphQL implementation | 2K | +2 | – | |
| 29 | enisdenjo/graphql-ws Coherent, zero-dependency, lazy, simple, GraphQL over WebSocket Protocol compliant server and client. | 1.9K | +2 | – | |
| 30 | graphql-dotnet/graphql-dotnet GraphQL for .NET | 6K | +1 | – | |
| 31 | graphql-python/graphene-django Build powerful, efficient, and flexible GraphQL APIs with seamless Django integration. | 4.4K | +1 | – | |
| 32 | mirumee/ariadne Python library for implementing GraphQL servers using schema-first approach. Created with :heart: by Mirumee | 2.3K | +1 | – | |
| 33 | marmelab/json-graphql-server Get a full fake GraphQL API with zero coding in less than 30 seconds. | 1.9K | +1 | – | |
| 34 | walmartlabs/lacinia GraphQL implementation in pure Clojure | 1.9K | +1 | – | |
| 35 | ExpediaGroup/graphql-kotlin Libraries for running GraphQL in Kotlin | 1.8K | +1 | – | |
| 36 | solidsnack/GraphpostgresQL GraphQL for Postgres | 1.1K | +1 | – | |
| 37 | IBM/openapi-to-graphqlarchived Translate APIs described by OpenAPI Specifications (OAS) into GraphQL | 1.6K | 0 | – | |
| 38 | tibor-kocsis/vertx-graphql-utils Vert.x GraphQL utils | 25 | 0 | – | |
| 39 | subquery/subql SubQuery is an Open, Flexible, Fast and Universal data indexing framework for web3. Our mission is to help developers create the decentralised products of the future. | 19K | -1 | – | |
| 40 | webonyx/graphql-php PHP implementation of the GraphQL specification based on the reference implementation in JavaScript | 4.7K | -2 | – |
Faster than the 30 days before
Net stars of the last 30 days are 2 or more times those of the 30 days before.
No repository with this Tag meets this rule now.
Slower than the 30 days before
Net stars of the last 30 days are 50% or less of those of the 30 days before.
No repository with this Tag meets this rule now.
New in the last 90 days
Created on GitHub in the last 90 days.
No repository with this Tag meets this rule now.
Older than 2 years, still releasing
Created more than 2 years ago, with a push in the last 7 days and a GitHub release in the last 30 days.
- hasura/graphql-engine32K · release today
- subquery/subql19K · release 6 days ago
- graphile/crystal13K · release 2 days ago
- 99designs/gqlgen11K · release 12 days ago
- graphql-hive/graphql-yoga8.5K · release 11 days ago
Last release more than 180 days ago
The newest GitHub release is more than 180 days old. A repository that never published a release is not in this list.
- apollographql/apollo-server14K · release 6 months ago
- graphql-go/graphql10K · release 3 years ago
- graphql-python/graphene8.2K · release last year
- MichalLytek/type-graphql8.1K · release 8 months ago
- rmosolgo/graphql-ruby5.4K · release last year
Top GitHub topics with this Tag
Primary languages
- TypeScript30%
- PHP13%
- Go10%
- Python10%
- C#5%
- Java5%
- JavaScript5%
- Kotlin5%
- Other or none18%
How a repository gets this Tag
An agent reads the description, the GitHub topics, and the start of the README of each repository. It chooses Tags only from the Tag list in the AwesomeRepos source code. For each Tag, it quotes the text. A code check keeps the Tag only when the quote is in that text. The page of each repository shows the quote of each of its Tags. A Tag does not rank repositories. It does not say that one repository can replace another. To report a wrong Tag, use "Report a problem with this page" on the page of the repository.
How the numbers are counted
All numbers come from the Star History of the repositories that have the Tag now. A period is a run of complete UTC days. All numbers on this page count only the repositories that AwesomeRepos shows in lists. A machine computes them each hour.
For each repository, a period counts only when Star History has each of its days, or when the repository was created in the period. Otherwise the table shows "–". The bars of a week with no complete data are grey.
The Pace is the net stars of a period divided by the net stars of the period before. It shows only when Star History covers each day of the period before, with at least 3 net stars a day on average.
The chart at the top adds up the net stars of all the repositories with the Tag. The darker area is the part from the Seed Dataset; the rest is from rising Admissions. A rising Admission comes into the Repository Index because it gained stars quickly. Its Star History before its Admission comes from the Repository Host. Thus the days before many rising Admissions are higher than they were for the repositories in the index at that time. The repositories of the Seed Dataset are a set that does not change.
The releases are the GitHub releases of each repository. The lists and the table do not rank repositories, and they do not say that one repository can replace another.