cockroachdb/drpc
Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.
- Current stars
- 2
- Activity since
- 2025
- Latest activity
- Jul 2025
Public star activity
- Last 30 days
- +1
- Last 90 days
- +2
- Actions / day
- 0.0
2 stars on July 31, 2025.
| Date | stars |
|---|---|
| May 25, 2025 | 1 |
| July 31, 2025 | 2 |
The commit history reads cockroachdb/drpc a second time
methodologyFix-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.
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 studioMaintenance, ownership and star-momentum signals, computed from the same commit and star history and embeddable as static images.
Reading badge evidence for cockroachdb/drpc.
Notes on cockroachdb/drpc
- How many stars does cockroachdb/drpc have?
- GitHub currently reports 2 stars for cockroachdb/drpc. The chart itself is rebuilt from historical star data, which records star actions and not unstars, so it reads as an attention signal rather than a net star count.
- What does recent star activity look like for drpc?
- gitdebt observed about 2 public star actions for cockroachdb/drpc over the latest 90 days of archive coverage (about 1 in the latest 30). This is an approximate attention signal, not a net-star count, because unstars are not present.
- Is drpc still active?
- Public archive data shows about 1 star actions for cockroachdb/drpc in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
- When was drpc created?
- cockroachdb/drpc was created on May 1, 2025. The first public star activity observed for cockroachdb/drpc is from May 2025.
Read drpc against a neighbour
comparison builderPut this drawing in your README
markdown for agentsThe 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.
<a href="https://gitdebt.com/cockroachdb/drpc?ref=readme">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/cockroachdb/drpc/chart.svg?theme=dark" />
<img alt="cockroachdb/drpc star history" src="https://api.gitdebt.com/api/repos/cockroachdb/drpc/chart.svg?theme=light" />
</picture>
</a>
<sub>Star history source: Historical star data · Covers through July 31, 2025 · Still updating — <a href="https://gitdebt.com/cockroachdb/drpc?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.