Skip to content

vitejs/rfcs-bot

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

Open on GitHub
Current stars
13
Activity since
2022
Latest activity
Jan 2024

Public star activity

Last 30 days
+1
Last 90 days
+1
Actions / day
0.0
Public star actions

stars from August 24, 2022 to January 8, 2024, peaking at 13.13 STARS1 YR 4 MO13JAN 2024AUG 2022

13 stars on January 8, 2024.

stars by date
Datestars
August 24, 20226
August 25, 20228
August 26, 202210
August 31, 202211
August 10, 202312
January 8, 202413

The last 90 days run behind its lifetime average, which is ordinary for a mature project.

The commit history reads vitejs/rfcs-bot 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 vitejs/rfcs-bot
File change frequency
File change frequency for vitejs/rfcs-bot
Bus factor
Bus factor for vitejs/rfcs-bot
Maintenance pulse
Maintenance pulse for vitejs/rfcs-bot
Contributors
Contributors for vitejs/rfcs-bot
Language activity
Language activity for vitejs/rfcs-bot
Commit activity
Commit activity for vitejs/rfcs-bot
Recent TODO/FIXME movement
Recent TODO/FIXME movement for vitejs/rfcs-bot

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 vitejs/rfcs-bot.

Notes on vitejs/rfcs-bot

How many stars does vitejs/rfcs-bot have?
GitHub currently reports 13 stars for vitejs/rfcs-bot. 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-bot?
gitdebt observed about 1 public star actions for vitejs/rfcs-bot 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-bot still active?
Public archive data shows about 1 star actions for vitejs/rfcs-bot 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-bot created?
vitejs/rfcs-bot was created on August 24, 2022. The first public star activity observed for vitejs/rfcs-bot is from Aug 2022.

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 · vitejs/rfcs-bot star history
<a href="https://gitdebt.com/vitejs/rfcs-bot?ref=readme">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/vitejs/rfcs-bot/chart.svg?theme=dark" />
    <img alt="vitejs/rfcs-bot star history" src="https://api.gitdebt.com/api/repos/vitejs/rfcs-bot/chart.svg?theme=light" />
  </picture>
</a>

<sub>Star history source: Historical star data · Covers through January 8, 2024 · Still updating — <a href="https://gitdebt.com/vitejs/rfcs-bot?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.