Portfolio concentration
91%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
29 repos
Visible snapshot
6 repositories updated in the last 90 days.
Leading language
Go
Portfolio mix
Go (11), Unknown (7), Python (4)
Average size
11
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
91%
of the visible star count comes from this organization's top three repositories.
11
stars per repository in this same snapshot.
Go
is the most common language here, with 6 repositories updated in the last 90 days.
Why this rank
This organization stands out because one flagship repo drives 84% of its visible star count.
Organization pages work best when you separate portfolio breadth from flagship concentration. In Dgraph's case, the visible top three repositories account for about 91% of total stars in this snapshot, which helps explain whether the organization is known for one breakout project or for a broader repeatable portfolio.
The dominant language mix here is Go (11), Unknown (7), Python (4). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.
| # | Repository | Language | Stars |
|---|---|---|---|
| 1 | dgraph-io/sroar Serialized Roaring Bitmaps | Go | 277 |
| 2 | dgraph-io/typhoon-ui ๐ typhoon-ui: Token-based React component library built using emotion. | TypeScript | 14 |
| 3 | dgraph-io/dgraph-experimental | Jupyter Notebook | 10 |
| 4 | dgraph-io/ops-runbooks Repository for operational runbooks | 4 | |
| 5 | dgraph-io/vlg Dgraph's Very Large Graph (WIP) Project | Go | 4 |
| 6 | dgraph-io/tweetsletter-workshop | JavaScript | 4 |
| 7 | dgraph-io/dgraph-day Learn graph database best practices from experts using Dgraph at scale in production and building the next generation of apps. Sign up for the FREE virtual event, April 15-16th. | 4 | |
| 8 | dgraph-io/dgdao dgdao โ typed Go client and DAO for Dgraph that writes to both local files and network clusters | Go | 3 |
| 9 | dgraph-io/dgdao-migrate A struct-first schema migration framework for Dgraph. | Go | 2 |
| 10 | dgraph-io/dgdao-gen Typed Go client code generator for Dgraph (dgraph-io/dgdao); formerly mlwelles/modusGraph-gen | Go | 2 |
| 11 | dgraph-io/roaring Roaring bitmaps in Go (golang) | Go | 2 |
| 12 | dgraph-io/dgdao-telemetry OpenTelemetry instrumentation for Dgraph clients (dgraph-io/dgdao); formerly mlwelles/modusGraph-telemetry | Go | 1 |
| 13 | dgraph-io/dgraph-locust locust testing framework for Dgraph, without initial data set to save space | Python | 1 |
| 14 | dgraph-io/sandbox Dgraph quick start and example code | 1 | |
| 15 | dgraph-io/argus Argus exercises Dgraph for correctness while benchmarking write and query performance. It drives DQL and GraphQL against the same cluster simultaneously, captures Go runtime and server-side statistics to CSV, and ends every run in a deterministic graph state so results are comparable across runs and versions. | Go | 0 |
| 16 | dgraph-io/renovate-config | 0 | |
| 17 | dgraph-io/analysisTools Tools to help analyze performance, log compaction, logs and other information from Dgraph systems | Python | 0 |
| 18 | dgraph-io/neoRatel | TypeScript | 0 |
| 19 | dgraph-io/gh-runner-autoscaling | Python | 0 |
| 20 | dgraph-io/admingui Small POC GUI for Cluster Admin | Python | 0 |
| 21 | dgraph-io/adityaARMfork Form ARM failures debugging | 0 | |
| 22 | dgraph-io/discuss-tutorial-angular | CSS | 0 |
| 23 | dgraph-io/caddyroute53 Caddy module: dns.providers.route53 | Go | 0 |
| 24 | dgraph-io/discourse-segment-theme-component | HTML | 0 |
| 25 | dgraph-io/federation-demo Demo of Apollo Federation | 0 | |
| 26 | dgraph-io/terraform-google-kubernetes-engine A Terraform module for configuring GKE clusters. | 0 | |
| 27 | dgraph-io/ldbc-queries | Groovy | 0 |
| 28 | dgraph-io/simdjson-go Golang port of simdjson: parsing gigabytes of JSON per second | Go | 0 |
| 29 | dgraph-io/tokenizer | Go | 0 |
Total stars are useful as a discovery signal, but they do not tell you whether a team maintains every repository equally. Pair this page with release cadence, maintainer activity, and the flagship concentration shown above before making adoption decisions.
For broader background on GitStar's ranking logic and editorial guidance, see Methodology & Editorial Standards.