Skip to content

cockroachdb/k8s

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

Open on GitHub
Stars
25
History since
2017
Latest star
May 2024

Star history

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

stars from June 12, 2017 to May 29, 2024, peaking at 25.25 STARS7 YR25MAY 2024JUN 2017

25 stars on May 29, 2024.

stars by date
Datestars
June 12, 20171
August 14, 20172
August 16, 20173
November 3, 20174
February 7, 20185
February 13, 20186
March 30, 20187
May 11, 20188
May 21, 20189
October 31, 201810
December 16, 201811
March 19, 201912
June 20, 201913
January 16, 202014
April 13, 202015
July 31, 202016
October 27, 202017
October 29, 202018
October 31, 202019
December 24, 202020
August 18, 202121
June 24, 202222
June 16, 202323
September 20, 202324
May 29, 202425

The last 90 days run in line with its lifetime average.

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

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/k8s.

Notes on cockroachdb/k8s

How many stars does cockroachdb/k8s have?
GitHub currently reports 25 stars for cockroachdb/k8s, with about 1 of them added in the last 90 days.
How fast is k8s growing?
cockroachdb/k8s 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 in line with its lifetime average growth pace.
Is k8s still active?
cockroachdb/k8s 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 k8s created?
cockroachdb/k8s was created on June 11, 2017 and earned its first GitHub star in Jun 2017.

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