Skip to content

drizzle-team/drizzle-studio-npm

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

Open on GitHub
Current stars
100
Activity since
2024
Latest activity
Apr 2026

Public star activity

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

stars from June 19, 2024 to April 18, 2026, peaking at 63.63 STARS1 YR 10 MO63APR 2026JUN 2024

63 stars on April 18, 2026.

stars by date
Datestars
June 19, 20242
June 20, 20243
June 26, 20244
July 6, 20245
July 8, 20246
August 2, 20247
August 20, 20248
August 21, 202410
September 1, 202411
September 5, 202412
September 6, 202413
September 9, 202414
September 14, 202415
September 21, 202416
October 2, 202417
October 26, 202418
November 4, 202419
November 5, 202420
November 19, 202421
November 27, 202422
December 17, 202423
December 26, 202424
January 12, 202525
January 21, 202526
February 17, 202527
March 5, 202528
March 6, 202530
March 7, 202531
March 15, 202532
March 22, 202533
March 26, 202534
April 9, 202535
April 11, 202536
April 15, 202537
May 4, 202539
May 9, 202540
June 27, 202541
June 30, 202542
July 10, 202543
July 25, 202544
August 6, 202545
August 12, 202547
August 26, 202548
August 27, 202549
August 29, 202550
September 1, 202551
September 5, 202552
September 26, 202553
November 23, 202554
December 3, 202555
December 22, 202556
December 31, 202557
February 8, 202658
February 26, 202659
March 7, 202660
March 8, 202661
April 10, 202662
April 18, 202663

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

The commit history reads drizzle-team/drizzle-studio-npm 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-studio-npm
File change frequency
File change frequency for drizzle-team/drizzle-studio-npm
Bus factor
Bus factor for drizzle-team/drizzle-studio-npm
Maintenance pulse
Maintenance pulse for drizzle-team/drizzle-studio-npm
Contributors
Contributors for drizzle-team/drizzle-studio-npm
Language activity
Language activity for drizzle-team/drizzle-studio-npm
Commit activity
Commit activity for drizzle-team/drizzle-studio-npm
Recent TODO/FIXME movement
Recent TODO/FIXME movement for drizzle-team/drizzle-studio-npm

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-studio-npm.

Notes on drizzle-team/drizzle-studio-npm

How many stars does drizzle-team/drizzle-studio-npm have?
GitHub currently reports 100 stars for drizzle-team/drizzle-studio-npm. 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-studio-npm?
gitdebt observed about 6 public star actions for drizzle-team/drizzle-studio-npm over the latest 90 days of archive coverage (about 2 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-studio-npm still active?
Public archive data shows about 2 star actions for drizzle-team/drizzle-studio-npm 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-studio-npm created?
drizzle-team/drizzle-studio-npm was created on June 12, 2024. The first public star activity observed for drizzle-team/drizzle-studio-npm is from Jun 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-studio-npm star history
<a href="https://gitdebt.com/drizzle-team/drizzle-studio-npm?ref=readme">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/drizzle-team/drizzle-studio-npm/chart.svg?theme=dark" />
    <img alt="drizzle-team/drizzle-studio-npm star history" src="https://api.gitdebt.com/api/repos/drizzle-team/drizzle-studio-npm/chart.svg?theme=light" />
  </picture>
</a>

<sub>Star history source: Historical star data · Covers through April 18, 2026 · Still updating — <a href="https://gitdebt.com/drizzle-team/drizzle-studio-npm?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.