How many stars does wez/kaleidoscopekeyboards have?

GitHub currently reports 4 stars for wez/kaleidoscopekeyboards. 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 kaleidoscopekeyboards?

gitdebt observed about 1 public star actions for wez/kaleidoscopekeyboards 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 faster than its lifetime average activity pace.

Is kaleidoscopekeyboards still active?

Public archive data shows about 1 star actions for wez/kaleidoscopekeyboards in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.

When was kaleidoscopekeyboards created?

wez/kaleidoscopekeyboards was created on April 30, 2017. The first public star activity observed for wez/kaleidoscopekeyboards is from May 2017.

wez/kaleidoscopekeyboards

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

Open on GitHub

Current stars: 4
Activity since: 2017
Latest activity: Sep 2020

Public star activity

Last 30 days: +1
Last 90 days: +1
Actions / day: 0.0

Public star actions

FromTo

stars by date
Date	stars
May 1, 2017	1
January 13, 2018	2
March 15, 2019	3
July 19, 2019	4
September 19, 2020	5

The last 90 days run ahead of this repository's lifetime average.

The commit history reads wez/kaleidoscopekeyboards 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 for wez/kaleidoscopekeyboards — Fix-labelled changes

File change frequency for wez/kaleidoscopekeyboards — File change frequency

Bus factor for wez/kaleidoscopekeyboards — Bus factor

Maintenance pulse for wez/kaleidoscopekeyboards — Maintenance pulse

Contributors for wez/kaleidoscopekeyboards — Contributors

Language activity for wez/kaleidoscopekeyboards — Language activity

Commit activity for wez/kaleidoscopekeyboards — Commit activity

Recent TODO/FIXME movement for wez/kaleidoscopekeyboards — Recent TODO/FIXME movement

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 wez/kaleidoscopekeyboards.

Notes on wez/kaleidoscopekeyboards

How many stars does wez/kaleidoscopekeyboards have?: GitHub currently reports 4 stars for wez/kaleidoscopekeyboards. 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 kaleidoscopekeyboards?: gitdebt observed about 1 public star actions for wez/kaleidoscopekeyboards 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 faster than its lifetime average activity pace.
Is kaleidoscopekeyboards still active?: Public archive data shows about 1 star actions for wez/kaleidoscopekeyboards in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
When was kaleidoscopekeyboards created?: wez/kaleidoscopekeyboards was created on April 30, 2017. The first public star activity observed for wez/kaleidoscopekeyboards is from May 2017.

Read kaleidoscopekeyboards against a neighbour

comparison builder

Compare with any repository

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 · wez/kaleidoscopekeyboards star history

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

<sub>Star history source: Historical star data · Covers through September 19, 2020 · Still updating — <a href="https://gitdebt.com/wez/kaleidoscopekeyboards?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.