gatsbyjs/rfcs
Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.
- Current stars
- 85
- Activity since
- 2018
- Latest activity
- Nov 2021
Public star activity
- Last 30 days
- +1
- Last 90 days
- +4
- Actions / day
- 0.1
91 stars on November 7, 2021.
| Date | stars |
|---|---|
| March 20, 2018 | 1 |
| April 6, 2018 | 4 |
| April 7, 2018 | 9 |
| April 8, 2018 | 12 |
| April 9, 2018 | 13 |
| April 10, 2018 | 16 |
| April 22, 2018 | 17 |
| April 23, 2018 | 18 |
| May 17, 2018 | 19 |
| June 9, 2018 | 20 |
| June 21, 2018 | 21 |
| June 22, 2018 | 22 |
| July 9, 2018 | 23 |
| July 10, 2018 | 24 |
| July 11, 2018 | 25 |
| July 19, 2018 | 26 |
| July 21, 2018 | 27 |
| July 25, 2018 | 28 |
| August 2, 2018 | 29 |
| August 4, 2018 | 30 |
| August 26, 2018 | 31 |
| August 27, 2018 | 32 |
| August 31, 2018 | 33 |
| September 14, 2018 | 34 |
| September 16, 2018 | 35 |
| September 18, 2018 | 36 |
| September 26, 2018 | 37 |
| September 29, 2018 | 38 |
| October 13, 2018 | 39 |
| October 21, 2018 | 40 |
| November 11, 2018 | 41 |
| December 2, 2018 | 42 |
| December 4, 2018 | 43 |
| December 6, 2018 | 44 |
| December 13, 2018 | 45 |
| December 20, 2018 | 46 |
| January 7, 2019 | 47 |
| January 24, 2019 | 48 |
| February 7, 2019 | 49 |
| February 11, 2019 | 50 |
| February 26, 2019 | 53 |
| March 17, 2019 | 54 |
| March 23, 2019 | 55 |
| April 3, 2019 | 56 |
| April 10, 2019 | 57 |
| April 22, 2019 | 62 |
| April 23, 2019 | 66 |
| April 28, 2019 | 68 |
| May 24, 2019 | 69 |
| June 21, 2019 | 70 |
| July 20, 2019 | 71 |
| September 12, 2019 | 72 |
| September 16, 2019 | 73 |
| September 18, 2019 | 75 |
| October 1, 2019 | 76 |
| October 7, 2019 | 77 |
| October 31, 2019 | 78 |
| November 21, 2019 | 79 |
| November 25, 2019 | 80 |
| April 14, 2020 | 81 |
| May 27, 2020 | 82 |
| August 18, 2020 | 83 |
| April 8, 2021 | 84 |
| June 11, 2021 | 85 |
| July 15, 2021 | 86 |
| July 22, 2021 | 87 |
| September 2, 2021 | 88 |
| September 3, 2021 | 89 |
| September 27, 2021 | 90 |
| November 7, 2021 | 91 |
The last 90 days run behind its lifetime average, which is ordinary for a mature project.
The commit history reads gatsbyjs/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 gatsbyjs/rfcs.
Notes on gatsbyjs/rfcs
- How many stars does gatsbyjs/rfcs have?
- GitHub currently reports 85 stars for gatsbyjs/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 gatsbyjs/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 rfcs still active?
- Public archive data shows about 1 star actions for gatsbyjs/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?
- gatsbyjs/rfcs was created on March 20, 2018. The first public star activity observed for gatsbyjs/rfcs is from Mar 2018.
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/gatsbyjs/rfcs?ref=readme">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/gatsbyjs/rfcs/chart.svg?theme=dark" />
<img alt="gatsbyjs/rfcs star history" src="https://api.gitdebt.com/api/repos/gatsbyjs/rfcs/chart.svg?theme=light" />
</picture>
</a>
<sub>Star history source: Historical star data · Covers through November 7, 2021 · Still updating — <a href="https://gitdebt.com/gatsbyjs/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.