drizzle-team/drizzle-studio-npm
Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.
- 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
63 stars on April 18, 2026.
| Date | stars |
|---|---|
| June 19, 2024 | 2 |
| June 20, 2024 | 3 |
| June 26, 2024 | 4 |
| July 6, 2024 | 5 |
| July 8, 2024 | 6 |
| August 2, 2024 | 7 |
| August 20, 2024 | 8 |
| August 21, 2024 | 10 |
| September 1, 2024 | 11 |
| September 5, 2024 | 12 |
| September 6, 2024 | 13 |
| September 9, 2024 | 14 |
| September 14, 2024 | 15 |
| September 21, 2024 | 16 |
| October 2, 2024 | 17 |
| October 26, 2024 | 18 |
| November 4, 2024 | 19 |
| November 5, 2024 | 20 |
| November 19, 2024 | 21 |
| November 27, 2024 | 22 |
| December 17, 2024 | 23 |
| December 26, 2024 | 24 |
| January 12, 2025 | 25 |
| January 21, 2025 | 26 |
| February 17, 2025 | 27 |
| March 5, 2025 | 28 |
| March 6, 2025 | 30 |
| March 7, 2025 | 31 |
| March 15, 2025 | 32 |
| March 22, 2025 | 33 |
| March 26, 2025 | 34 |
| April 9, 2025 | 35 |
| April 11, 2025 | 36 |
| April 15, 2025 | 37 |
| May 4, 2025 | 39 |
| May 9, 2025 | 40 |
| June 27, 2025 | 41 |
| June 30, 2025 | 42 |
| July 10, 2025 | 43 |
| July 25, 2025 | 44 |
| August 6, 2025 | 45 |
| August 12, 2025 | 47 |
| August 26, 2025 | 48 |
| August 27, 2025 | 49 |
| August 29, 2025 | 50 |
| September 1, 2025 | 51 |
| September 5, 2025 | 52 |
| September 26, 2025 | 53 |
| November 23, 2025 | 54 |
| December 3, 2025 | 55 |
| December 22, 2025 | 56 |
| December 31, 2025 | 57 |
| February 8, 2026 | 58 |
| February 26, 2026 | 59 |
| March 7, 2026 | 60 |
| March 8, 2026 | 61 |
| April 10, 2026 | 62 |
| April 18, 2026 | 63 |
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
methodologyFix-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.
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 studioMaintenance, 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.
Read drizzle-studio-npm against a neighbour
comparison builderPut this drawing in your README
markdown for agentsThe 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.
<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.