bevyengine/rfcs
Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.
- Current stars
- 117
- Activity since
- 2021
- Latest activity
- Jun 2025
Public star activity
- Last 30 days
- +3
- Last 90 days
- +4
- Actions / day
- 0.1
128 stars on June 28, 2025.
| Date | stars |
|---|---|
| April 14, 2021 | 3 |
| April 15, 2021 | 4 |
| April 16, 2021 | 5 |
| April 17, 2021 | 6 |
| April 22, 2021 | 11 |
| April 23, 2021 | 14 |
| April 30, 2021 | 15 |
| May 25, 2021 | 16 |
| May 27, 2021 | 18 |
| June 6, 2021 | 19 |
| June 17, 2021 | 20 |
| June 22, 2021 | 21 |
| August 10, 2021 | 23 |
| August 11, 2021 | 24 |
| August 19, 2021 | 25 |
| September 4, 2021 | 26 |
| September 15, 2021 | 27 |
| September 28, 2021 | 28 |
| October 5, 2021 | 29 |
| October 30, 2021 | 30 |
| November 14, 2021 | 32 |
| December 13, 2021 | 33 |
| January 15, 2022 | 34 |
| January 19, 2022 | 35 |
| January 24, 2022 | 36 |
| January 25, 2022 | 37 |
| January 27, 2022 | 38 |
| February 1, 2022 | 39 |
| February 3, 2022 | 40 |
| February 21, 2022 | 41 |
| March 1, 2022 | 42 |
| March 5, 2022 | 44 |
| March 6, 2022 | 45 |
| March 8, 2022 | 46 |
| March 17, 2022 | 47 |
| March 25, 2022 | 48 |
| April 1, 2022 | 49 |
| April 15, 2022 | 50 |
| April 20, 2022 | 51 |
| April 30, 2022 | 52 |
| May 5, 2022 | 53 |
| May 7, 2022 | 54 |
| May 13, 2022 | 55 |
| May 23, 2022 | 56 |
| June 2, 2022 | 57 |
| June 26, 2022 | 58 |
| July 7, 2022 | 59 |
| July 11, 2022 | 60 |
| July 30, 2022 | 61 |
| August 16, 2022 | 62 |
| September 4, 2022 | 63 |
| September 17, 2022 | 67 |
| September 21, 2022 | 68 |
| October 2, 2022 | 69 |
| October 3, 2022 | 70 |
| October 29, 2022 | 71 |
| November 5, 2022 | 72 |
| November 15, 2022 | 73 |
| November 17, 2022 | 74 |
| November 21, 2022 | 75 |
| November 25, 2022 | 76 |
| November 27, 2022 | 77 |
| November 29, 2022 | 78 |
| December 11, 2022 | 79 |
| December 23, 2022 | 80 |
| January 4, 2023 | 81 |
| January 8, 2023 | 82 |
| February 15, 2023 | 83 |
| February 28, 2023 | 84 |
| March 3, 2023 | 86 |
| March 4, 2023 | 87 |
| March 9, 2023 | 88 |
| March 10, 2023 | 89 |
| March 12, 2023 | 90 |
| April 3, 2023 | 91 |
| July 3, 2023 | 92 |
| July 23, 2023 | 93 |
| July 29, 2023 | 94 |
| July 30, 2023 | 95 |
| August 24, 2023 | 96 |
| September 28, 2023 | 97 |
| September 30, 2023 | 98 |
| October 15, 2023 | 99 |
| October 16, 2023 | 100 |
| November 29, 2023 | 101 |
| December 12, 2023 | 102 |
| December 13, 2023 | 103 |
| January 13, 2024 | 104 |
| February 19, 2024 | 105 |
| February 28, 2024 | 106 |
| March 22, 2024 | 107 |
| March 29, 2024 | 108 |
| April 3, 2024 | 109 |
| April 5, 2024 | 110 |
| April 11, 2024 | 111 |
| April 18, 2024 | 112 |
| May 9, 2024 | 113 |
| May 25, 2024 | 114 |
| July 25, 2024 | 115 |
| August 16, 2024 | 116 |
| August 23, 2024 | 117 |
| August 29, 2024 | 118 |
| September 22, 2024 | 119 |
| October 18, 2024 | 121 |
| November 7, 2024 | 122 |
| December 26, 2024 | 123 |
| February 1, 2025 | 124 |
| May 28, 2025 | 125 |
| June 11, 2025 | 126 |
| June 26, 2025 | 127 |
| June 28, 2025 | 128 |
The last 90 days run behind its lifetime average, which is ordinary for a mature project.
Observed activity milestones: 100 around Oct 2023
The commit history reads bevyengine/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 bevyengine/rfcs.
Notes on bevyengine/rfcs
- How many stars does bevyengine/rfcs have?
- GitHub currently reports 117 stars for bevyengine/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 rfcs?
- gitdebt observed about 4 public star actions for bevyengine/rfcs over the latest 90 days of archive coverage (about 3 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 rfcs still active?
- Public archive data shows about 3 star actions for bevyengine/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 rfcs created?
- bevyengine/rfcs was created on April 14, 2021. The first public star activity observed for bevyengine/rfcs is from Apr 2021.
Read 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/bevyengine/rfcs?ref=readme">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/bevyengine/rfcs/chart.svg?theme=dark" />
<img alt="bevyengine/rfcs star history" src="https://api.gitdebt.com/api/repos/bevyengine/rfcs/chart.svg?theme=light" />
</picture>
</a>
<sub>Star history source: Historical star data · Covers through June 28, 2025 · Still updating — <a href="https://gitdebt.com/bevyengine/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.