Skip to content

cockroachdb/stress

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

Open on GitHub
Stars
5
History since
2019
Latest star
Jun 2023

Star history

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

stars from December 10, 2019 to June 16, 2023, peaking at 5.5 STARS3 YR 6 MO5JUN 2023DEC 2019

5 stars on June 16, 2023.

stars by date
Datestars
December 10, 20191
February 13, 20202
April 13, 20203
January 28, 20224
June 16, 20235

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

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

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

Notes on cockroachdb/stress

How many stars does cockroachdb/stress have?
GitHub currently reports 5 stars for cockroachdb/stress, with about 1 of them added in the last 90 days.
How fast is stress growing?
cockroachdb/stress 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 stress still active?
cockroachdb/stress 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 stress created?
cockroachdb/stress was created on January 27, 2016 and earned its first GitHub star in Dec 2019.

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