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