How many stars does cockroachdb/c-rocksdb have?

GitHub currently reports 43 stars for cockroachdb/c-rocksdb, with about 2 of them added in the last 90 days.

How fast is c-rocksdb growing?

cockroachdb/c-rocksdb gained about 2 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-rocksdb still active?

cockroachdb/c-rocksdb 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-rocksdb created?

cockroachdb/c-rocksdb was created on February 24, 2015 and earned its first GitHub star in Mar 2015.

cockroachdb/c-rocksdb

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

Open on GitHub

Stars: 43
History since: 2015
Latest star: Sep 2023

Star history

Last 30 days: +1
Last 90 days: +2
Stars / day: 0.0

Cumulative stars

FromTo

stars by date
Date	stars
March 12, 2015	1
August 26, 2015	2
September 16, 2015	3
September 24, 2015	4
December 5, 2015	5
December 17, 2015	6
April 10, 2016	7
April 23, 2016	9
April 24, 2016	10
April 29, 2016	11
May 5, 2016	12
June 4, 2016	13
August 11, 2016	14
August 15, 2016	15
August 23, 2016	16
August 25, 2016	17
September 7, 2016	18
September 8, 2016	19
September 19, 2016	20
October 13, 2016	21
October 27, 2016	22
November 8, 2016	23
November 13, 2016	24
December 27, 2016	25
January 2, 2017	26
February 14, 2017	27
February 18, 2017	28
February 19, 2017	29
March 29, 2017	30
April 2, 2017	31
December 14, 2017	32
February 9, 2018	33
August 26, 2018	34
February 25, 2019	35
June 23, 2020	36
July 29, 2020	37
April 26, 2021	38
October 22, 2021	39
October 20, 2022	40
June 19, 2023	41
August 17, 2023	42
September 20, 2023	43

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

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

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

Bus factor for cockroachdb/c-rocksdb — Bus factor

Maintenance pulse for cockroachdb/c-rocksdb — Maintenance pulse

Contributors for cockroachdb/c-rocksdb — Contributors

Language activity for cockroachdb/c-rocksdb — Language activity

Commit activity for cockroachdb/c-rocksdb — Commit activity

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

Notes on cockroachdb/c-rocksdb

How many stars does cockroachdb/c-rocksdb have?: GitHub currently reports 43 stars for cockroachdb/c-rocksdb, with about 2 of them added in the last 90 days.
How fast is c-rocksdb growing?: cockroachdb/c-rocksdb gained about 2 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-rocksdb still active?: cockroachdb/c-rocksdb 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-rocksdb created?: cockroachdb/c-rocksdb was created on February 24, 2015 and earned its first GitHub star in Mar 2015.

Read c-rocksdb 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-rocksdb star history

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