Skip to content

cockroachdb/rpc-bench

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

Open on GitHub
Stars
87
History since
2015
Latest star
Oct 2024

Star history

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

stars from June 5, 2015 to October 5, 2024, peaking at 87.87 STARS9 YR 4 MO87OCT 2024JUN 2015

87 stars on October 5, 2024.

stars by date
Datestars
June 5, 20152
June 7, 20153
June 8, 20158
June 17, 20159
June 21, 201510
September 24, 201511
October 13, 201512
October 14, 201513
November 4, 201514
December 15, 201515
March 29, 201616
April 14, 201617
April 27, 201618
May 26, 201619
June 2, 201620
June 11, 201621
July 5, 201622
July 25, 201623
September 3, 201624
November 27, 201625
November 28, 201626
December 12, 201627
January 25, 201728
May 17, 201729
September 12, 201730
November 13, 201731
November 21, 201733
January 19, 201834
January 20, 201835
February 21, 201836
April 10, 201838
April 11, 201840
April 23, 201841
April 24, 201842
May 21, 201843
May 23, 201844
June 21, 201845
June 25, 201846
August 22, 201847
September 9, 201848
October 10, 201849
November 10, 201850
November 16, 201851
December 30, 201852
February 17, 201953
May 29, 201954
August 27, 201955
April 28, 202056
May 1, 202057
May 18, 202058
October 27, 202059
November 12, 202060
November 20, 202061
January 15, 202165
January 17, 202166
February 7, 202167
April 2, 202168
April 19, 202176
April 20, 202177
April 21, 202178
May 26, 202179
September 2, 202180
October 3, 202181
September 21, 202282
December 18, 202283
December 24, 202284
June 18, 202385
April 21, 202486
October 5, 202487

The last 90 days run behind its lifetime average, which is ordinary for a mature project.

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

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/rpc-bench.

Notes on cockroachdb/rpc-bench

How many stars does cockroachdb/rpc-bench have?
GitHub currently reports 87 stars for cockroachdb/rpc-bench, with about 1 of them added in the last 90 days.
How fast is rpc-bench growing?
cockroachdb/rpc-bench 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 below its lifetime average growth pace, which is common for mature projects.
Is rpc-bench still active?
cockroachdb/rpc-bench 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 rpc-bench created?
cockroachdb/rpc-bench was created on June 2, 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/rpc-bench star history
<a href="https://gitdebt.com/cockroachdb/rpc-bench?ref=readme">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/cockroachdb/rpc-bench/chart.svg?theme=dark" />
    <img alt="cockroachdb/rpc-bench star history" src="https://api.gitdebt.com/api/repos/cockroachdb/rpc-bench/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/rpc-bench?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.