Skip to content

cockroachdb/c-snappy

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

Open on GitHub
Stars
21
History since
2015
Latest star
Sep 2023

Star history

Last 30 days
+1
Last 90 days
+1
Stars / day
0.0
Cumulative stars

stars from June 8, 2015 to September 23, 2023, peaking at 21.21 STARS8 YR 4 MO21SEP 2023JUN 2015

21 stars on September 23, 2023.

stars by date
Datestars
June 8, 20152
June 9, 20153
April 23, 20169
April 24, 201610
December 30, 201611
January 25, 201712
December 14, 201713
January 21, 201814
February 9, 201815
March 20, 201816
October 17, 201817
October 27, 202018
November 2, 202019
June 19, 202320
September 23, 202321

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

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

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-snappy.

Notes on cockroachdb/c-snappy

How many stars does cockroachdb/c-snappy have?
GitHub currently reports 21 stars for cockroachdb/c-snappy, with about 1 of them added in the last 90 days.
How fast is c-snappy growing?
cockroachdb/c-snappy gained about 1 stars over the last 90 days of its history (about 1 in the last 30) — figures are approximate for older repos, whose star history is downsampled. That's faster than its lifetime average growth pace.
Is c-snappy still active?
cockroachdb/c-snappy is still attracting attention — about 1 new GitHub stars in the most recent 30 days of its history. For commit-level signals, see the commit activity heatmap, commit trend, and contributors charts on this page.
When was c-snappy created?
cockroachdb/c-snappy was created on February 25, 2015 and earned its first GitHub star in Jun 2015.

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

<sub>Star history source: GitHub star history · Covers through November 14, 2026 · Still updating — <a href="https://gitdebt.com/cockroachdb/c-snappy?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.