Skip to content

drizzle-team/drizzle-graphql

Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.

Open on GitHub
Current stars
89
Activity since
2024
Latest activity
Mar 2026

Public star activity

Last 30 days
+1
Last 90 days
+1
Actions / day
0.1
Public star actions

stars from March 27, 2024 to March 4, 2026, peaking at 76.76 STARS1 YR 11 MO76MAR 2026MAR 2024

76 stars on March 4, 2026.

stars by date
Datestars
March 27, 20241
April 7, 20242
April 12, 20243
April 15, 20244
April 21, 20248
April 22, 202412
April 23, 202413
April 24, 202414
April 25, 202415
April 26, 202416
April 29, 202417
May 3, 202418
May 4, 202420
May 6, 202421
May 12, 202423
May 13, 202424
May 15, 202425
May 20, 202427
May 22, 202428
May 26, 202429
May 30, 202431
June 5, 202432
June 22, 202433
July 6, 202434
July 25, 202435
August 1, 202436
August 9, 202437
August 12, 202438
August 18, 202439
August 19, 202440
August 26, 202441
August 31, 202442
September 16, 202443
September 17, 202444
September 19, 202445
September 20, 202446
October 7, 202447
October 28, 202448
October 29, 202449
November 6, 202450
November 15, 202451
November 23, 202452
November 29, 202453
December 16, 202454
December 24, 202455
December 29, 202456
January 4, 202557
January 5, 202558
January 31, 202559
February 22, 202560
March 24, 202562
April 11, 202563
April 14, 202564
April 20, 202565
May 18, 202567
May 19, 202568
May 27, 202569
June 15, 202570
June 18, 202571
July 9, 202572
August 4, 202573
August 5, 202574
August 6, 202575
March 4, 202676

The last 90 days run behind its lifetime average, which is ordinary for a mature project.

The commit history reads drizzle-team/drizzle-graphql a second time

methodology

Fix-labelled changes, file change frequency, ownership concentration and maintenance cadence, each computed from this repository's analyzed commit window. None of them is derived from stars, which is why they are allowed to disagree with the curve above.

Fix-labelled changes
Fix-labelled changes for drizzle-team/drizzle-graphql
File change frequency
File change frequency for drizzle-team/drizzle-graphql
Bus factor
Bus factor for drizzle-team/drizzle-graphql
Maintenance pulse
Maintenance pulse for drizzle-team/drizzle-graphql
Contributors
Contributors for drizzle-team/drizzle-graphql
Language activity
Language activity for drizzle-team/drizzle-graphql
Commit activity
Commit activity for drizzle-team/drizzle-graphql
Recent TODO/FIXME movement
Recent TODO/FIXME movement for drizzle-team/drizzle-graphql

Attention is not adoption.

Stars against usage

No published package was detected for this repository, so there is nothing to lay over star growth.

Earned badges

badge studio

Maintenance, ownership and star-momentum signals, computed from the same commit and star history and embeddable as static images.

Reading badge evidence for drizzle-team/drizzle-graphql.

Notes on drizzle-team/drizzle-graphql

How many stars does drizzle-team/drizzle-graphql have?
GitHub currently reports 89 stars for drizzle-team/drizzle-graphql. The chart itself is rebuilt from historical star data, which records star actions and not unstars, so it reads as an attention signal rather than a net star count.
What does recent star activity look like for drizzle-graphql?
gitdebt observed about 1 public star actions for drizzle-team/drizzle-graphql over the latest 90 days of archive coverage (about 1 in the latest 30). This is an approximate attention signal, not a net-star count, because unstars are not present. That's below its lifetime average activity pace, which is common for mature projects.
Is drizzle-graphql still active?
Public archive data shows about 1 star actions for drizzle-team/drizzle-graphql in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
When was drizzle-graphql created?
drizzle-team/drizzle-graphql was created on March 19, 2024. The first public star activity observed for drizzle-team/drizzle-graphql is from Mar 2024.

Put this drawing in your README

markdown for agents

The block below publishes the chart with its source and coverage date stated beside it — the same three facts the title block above shows, as text a reader can check. The prompt underneath hands a coding agent the badges and repo-health charts as well.

README.md · drizzle-team/drizzle-graphql star history
<a href="https://gitdebt.com/drizzle-team/drizzle-graphql?ref=readme">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/drizzle-team/drizzle-graphql/chart.svg?theme=dark" />
    <img alt="drizzle-team/drizzle-graphql star history" src="https://api.gitdebt.com/api/repos/drizzle-team/drizzle-graphql/chart.svg?theme=light" />
  </picture>
</a>

<sub>Star history source: Historical star data · Covers through March 4, 2026 · Still updating — <a href="https://gitdebt.com/drizzle-team/drizzle-graphql?ref=readme">gitdebt</a></sub>

Light and dark variants, alt text, and one provenance line. Provenance is text in your README, never baked into the image URL, so the chart stays cacheable.

Paste it into Claude Code, Cursor, Codex, or any coding agent with your checkout open. It carries the measured numbers, the exact snippets, and the rules — including replacing an existing star-history widget in place rather than stacking a second chart under it.