How many stars does cockroachdb/c-lz4 have?

GitHub currently reports 10 stars for cockroachdb/c-lz4. 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 c-lz4?

gitdebt observed about 1 public star actions for cockroachdb/c-lz4 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 c-lz4 still active?

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

When was c-lz4 created?

cockroachdb/c-lz4 was created on April 27, 2015. The first public star activity observed for cockroachdb/c-lz4 is from Sep 2015.

cockroachdb/c-lz4

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

Open on GitHub

Current stars: 10
Activity since: 2015
Latest activity: Jun 2023

Public star activity

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

Public star actions

FromTo

stars by date
Date	stars
September 24, 2015	1
November 26, 2015	2
December 5, 2015	3
July 14, 2016	4
December 14, 2017	5
February 9, 2018	6
April 13, 2020	7
September 15, 2020	8
October 28, 2020	9
April 25, 2022	10
June 20, 2023	11

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

The commit history reads cockroachdb/c-lz4 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 cockroachdb/c-lz4 — Fix-labelled changes

File change frequency for cockroachdb/c-lz4 — File change frequency

Bus factor for cockroachdb/c-lz4 — Bus factor

Maintenance pulse for cockroachdb/c-lz4 — Maintenance pulse

Contributors for cockroachdb/c-lz4 — Contributors

Language activity for cockroachdb/c-lz4 — Language activity

Commit activity for cockroachdb/c-lz4 — Commit activity

Recent TODO/FIXME movement for cockroachdb/c-lz4 — 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 cockroachdb/c-lz4.

Notes on cockroachdb/c-lz4

How many stars does cockroachdb/c-lz4 have?: GitHub currently reports 10 stars for cockroachdb/c-lz4. 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 c-lz4?: gitdebt observed about 1 public star actions for cockroachdb/c-lz4 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 c-lz4 still active?: Public archive data shows about 1 star actions for cockroachdb/c-lz4 in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
When was c-lz4 created?: cockroachdb/c-lz4 was created on April 27, 2015. The first public star activity observed for cockroachdb/c-lz4 is from Sep 2015.

Read c-lz4 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 · cockroachdb/c-lz4 star history

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

<sub>Star history source: Historical star data · Covers through June 20, 2023 · Still updating — <a href="https://gitdebt.com/cockroachdb/c-lz4?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.