tokio-rs/tokio-rfcs
Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.
- Current stars
- 22
- Activity since
- 2017
- Latest activity
- May 2020
Public star activity
- Last 30 days
- +1
- Last 90 days
- +1
- Actions / day
- 0.0
25 stars on May 15, 2020.
| Date | stars |
|---|---|
| September 27, 2017 | 2 |
| September 29, 2017 | 5 |
| October 19, 2017 | 6 |
| November 2, 2017 | 7 |
| November 7, 2017 | 8 |
| November 15, 2017 | 10 |
| December 2, 2017 | 11 |
| December 7, 2017 | 12 |
| December 19, 2017 | 13 |
| January 5, 2018 | 14 |
| January 23, 2018 | 15 |
| January 24, 2018 | 16 |
| February 8, 2018 | 17 |
| February 10, 2018 | 18 |
| March 28, 2018 | 19 |
| June 3, 2018 | 20 |
| November 14, 2018 | 21 |
| December 6, 2018 | 22 |
| May 31, 2019 | 23 |
| June 3, 2019 | 24 |
| May 15, 2020 | 25 |
The last 90 days run behind its lifetime average, which is ordinary for a mature project.
The commit history reads tokio-rs/tokio-rfcs 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 tokio-rs/tokio-rfcs.
Notes on tokio-rs/tokio-rfcs
- How many stars does tokio-rs/tokio-rfcs have?
- GitHub currently reports 22 stars for tokio-rs/tokio-rfcs. 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 tokio-rfcs?
- gitdebt observed about 1 public star actions for tokio-rs/tokio-rfcs 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. That's below its lifetime average activity pace, which is common for mature projects.
- Is tokio-rfcs still active?
- Public archive data shows about 1 star actions for tokio-rs/tokio-rfcs in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
- When was tokio-rfcs created?
- tokio-rs/tokio-rfcs was created on August 17, 2017. The first public star activity observed for tokio-rs/tokio-rfcs is from Sep 2017.
Read tokio-rfcs 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/tokio-rs/tokio-rfcs?ref=readme">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/tokio-rs/tokio-rfcs/chart.svg?theme=dark" />
<img alt="tokio-rs/tokio-rfcs star history" src="https://api.gitdebt.com/api/repos/tokio-rs/tokio-rfcs/chart.svg?theme=light" />
</picture>
</a>
<sub>Star history source: Historical star data · Covers through May 15, 2020 · Still updating — <a href="https://gitdebt.com/tokio-rs/tokio-rfcs?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.