tokio-rs/async-backtrace
Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.
- Current stars
- 208
- Activity since
- 2022
- Latest activity
- May 2026
Public star activity
- Last 30 days
- +2
- Last 90 days
- +2
- Actions / day
- 0.2
199 stars on May 9, 2026.
| Date | stars |
|---|---|
| October 20, 2022 | 1 |
| October 21, 2022 | 3 |
| October 24, 2022 | 5 |
| October 26, 2022 | 6 |
| October 31, 2022 | 18 |
| November 1, 2022 | 55 |
| November 2, 2022 | 76 |
| November 3, 2022 | 86 |
| November 4, 2022 | 91 |
| November 5, 2022 | 92 |
| November 6, 2022 | 93 |
| November 7, 2022 | 95 |
| November 8, 2022 | 96 |
| November 9, 2022 | 97 |
| November 10, 2022 | 98 |
| November 12, 2022 | 101 |
| November 14, 2022 | 102 |
| November 15, 2022 | 103 |
| November 16, 2022 | 105 |
| November 22, 2022 | 106 |
| November 24, 2022 | 107 |
| November 26, 2022 | 108 |
| December 10, 2022 | 110 |
| January 5, 2023 | 112 |
| January 10, 2023 | 113 |
| January 11, 2023 | 114 |
| January 12, 2023 | 115 |
| January 25, 2023 | 116 |
| February 15, 2023 | 117 |
| February 23, 2023 | 118 |
| February 24, 2023 | 122 |
| February 28, 2023 | 123 |
| March 12, 2023 | 124 |
| March 22, 2023 | 125 |
| March 25, 2023 | 126 |
| March 27, 2023 | 127 |
| April 20, 2023 | 128 |
| April 28, 2023 | 129 |
| June 6, 2023 | 130 |
| June 17, 2023 | 133 |
| June 24, 2023 | 134 |
| June 26, 2023 | 135 |
| June 27, 2023 | 137 |
| June 28, 2023 | 138 |
| June 30, 2023 | 139 |
| July 4, 2023 | 140 |
| July 5, 2023 | 142 |
| July 6, 2023 | 143 |
| July 7, 2023 | 144 |
| July 13, 2023 | 145 |
| August 1, 2023 | 146 |
| August 18, 2023 | 147 |
| August 21, 2023 | 148 |
| September 3, 2023 | 149 |
| October 31, 2023 | 150 |
| November 7, 2023 | 151 |
| November 8, 2023 | 152 |
| December 1, 2023 | 153 |
| January 8, 2024 | 154 |
| January 13, 2024 | 155 |
| January 24, 2024 | 157 |
| January 25, 2024 | 160 |
| January 26, 2024 | 161 |
| January 28, 2024 | 162 |
| February 4, 2024 | 163 |
| February 10, 2024 | 164 |
| February 12, 2024 | 166 |
| February 13, 2024 | 168 |
| February 21, 2024 | 169 |
| February 24, 2024 | 170 |
| March 3, 2024 | 171 |
| March 19, 2024 | 172 |
| May 4, 2024 | 173 |
| June 1, 2024 | 174 |
| July 1, 2024 | 176 |
| July 12, 2024 | 177 |
| July 24, 2024 | 178 |
| September 13, 2024 | 179 |
| October 24, 2024 | 180 |
| December 6, 2024 | 181 |
| December 9, 2024 | 182 |
| December 19, 2024 | 183 |
| January 1, 2025 | 185 |
| February 12, 2025 | 186 |
| March 22, 2025 | 187 |
| April 11, 2025 | 188 |
| May 9, 2025 | 189 |
| May 15, 2025 | 190 |
| June 13, 2025 | 191 |
| June 21, 2025 | 192 |
| July 4, 2025 | 193 |
| August 17, 2025 | 194 |
| October 8, 2025 | 195 |
| October 28, 2025 | 196 |
| January 9, 2026 | 197 |
| April 16, 2026 | 198 |
| May 9, 2026 | 199 |
The last 90 days run behind its lifetime average, which is ordinary for a mature project.
Observed activity milestones: 100 around Nov 2022
The commit history reads tokio-rs/async-backtrace 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/async-backtrace.
Notes on tokio-rs/async-backtrace
- How many stars does tokio-rs/async-backtrace have?
- GitHub currently reports 208 stars for tokio-rs/async-backtrace. 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 async-backtrace?
- gitdebt observed about 2 public star actions for tokio-rs/async-backtrace over the latest 90 days of archive coverage (about 2 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 async-backtrace still active?
- Public archive data shows about 2 star actions for tokio-rs/async-backtrace in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
- When was async-backtrace created?
- tokio-rs/async-backtrace was created on September 26, 2022. The first public star activity observed for tokio-rs/async-backtrace is from Oct 2022.
Read async-backtrace 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/async-backtrace?ref=readme">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/tokio-rs/async-backtrace/chart.svg?theme=dark" />
<img alt="tokio-rs/async-backtrace star history" src="https://api.gitdebt.com/api/repos/tokio-rs/async-backtrace/chart.svg?theme=light" />
</picture>
</a>
<sub>Star history source: Historical star data · Covers through May 9, 2026 · Still updating — <a href="https://gitdebt.com/tokio-rs/async-backtrace?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.