Skip to content

gatsbyjs/rfcs

Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.

Open on GitHub
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
Public star actions

stars from March 20, 2018 to November 7, 2021, peaking at 91.91 STARS3 YR 8 MO91NOV 2021MAR 2018

91 stars on November 7, 2021.

stars by date
Datestars
March 20, 20181
April 6, 20184
April 7, 20189
April 8, 201812
April 9, 201813
April 10, 201816
April 22, 201817
April 23, 201818
May 17, 201819
June 9, 201820
June 21, 201821
June 22, 201822
July 9, 201823
July 10, 201824
July 11, 201825
July 19, 201826
July 21, 201827
July 25, 201828
August 2, 201829
August 4, 201830
August 26, 201831
August 27, 201832
August 31, 201833
September 14, 201834
September 16, 201835
September 18, 201836
September 26, 201837
September 29, 201838
October 13, 201839
October 21, 201840
November 11, 201841
December 2, 201842
December 4, 201843
December 6, 201844
December 13, 201845
December 20, 201846
January 7, 201947
January 24, 201948
February 7, 201949
February 11, 201950
February 26, 201953
March 17, 201954
March 23, 201955
April 3, 201956
April 10, 201957
April 22, 201962
April 23, 201966
April 28, 201968
May 24, 201969
June 21, 201970
July 20, 201971
September 12, 201972
September 16, 201973
September 18, 201975
October 1, 201976
October 7, 201977
October 31, 201978
November 21, 201979
November 25, 201980
April 14, 202081
May 27, 202082
August 18, 202083
April 8, 202184
June 11, 202185
July 15, 202186
July 22, 202187
September 2, 202188
September 3, 202189
September 27, 202190
November 7, 202191

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

methodology

Fix-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.

Fix-labelled changes
Fix-labelled changes for gatsbyjs/rfcs
File change frequency
File change frequency for gatsbyjs/rfcs
Bus factor
Bus factor for gatsbyjs/rfcs
Maintenance pulse
Maintenance pulse for gatsbyjs/rfcs
Contributors
Contributors for gatsbyjs/rfcs
Language activity
Language activity for gatsbyjs/rfcs
Commit activity
Commit activity for gatsbyjs/rfcs
Recent TODO/FIXME movement
Recent TODO/FIXME movement for gatsbyjs/rfcs

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 studio

Maintenance, 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.

Put this drawing in your README

markdown for agents

The 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.

README.md · gatsbyjs/rfcs star history
<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.