vercel/components.build
Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.
- Current stars
- 793
- Activity since
- 2025
- Latest activity
- Sep 2026
Public star activity
- Last 30 days
- +1
- Last 90 days
- +1
- Actions / day
- 0.8
274 stars on September 6, 2026.
| Date | stars |
|---|---|
| October 14, 2025 | 13 |
| October 15, 2025 | 86 |
| October 16, 2025 | 123 |
| October 17, 2025 | 152 |
| October 18, 2025 | 183 |
| October 19, 2025 | 196 |
| October 20, 2025 | 202 |
| October 21, 2025 | 206 |
| October 22, 2025 | 208 |
| October 23, 2025 | 210 |
| October 25, 2025 | 213 |
| October 26, 2025 | 214 |
| October 27, 2025 | 215 |
| November 1, 2025 | 216 |
| November 2, 2025 | 217 |
| November 3, 2025 | 218 |
| November 4, 2025 | 220 |
| November 5, 2025 | 221 |
| November 12, 2025 | 223 |
| November 16, 2025 | 224 |
| November 17, 2025 | 225 |
| November 18, 2025 | 226 |
| November 21, 2025 | 227 |
| November 29, 2025 | 236 |
| November 30, 2025 | 237 |
| December 4, 2025 | 238 |
| December 7, 2025 | 239 |
| December 8, 2025 | 240 |
| December 10, 2025 | 241 |
| December 18, 2025 | 242 |
| December 27, 2025 | 245 |
| December 28, 2025 | 247 |
| January 7, 2026 | 248 |
| January 8, 2026 | 249 |
| January 12, 2026 | 250 |
| January 25, 2026 | 251 |
| January 27, 2026 | 252 |
| January 30, 2026 | 253 |
| February 4, 2026 | 258 |
| February 5, 2026 | 260 |
| February 6, 2026 | 261 |
| February 14, 2026 | 262 |
| February 18, 2026 | 263 |
| February 20, 2026 | 264 |
| March 9, 2026 | 265 |
| March 17, 2026 | 266 |
| April 4, 2026 | 267 |
| April 5, 2026 | 268 |
| April 18, 2026 | 269 |
| April 20, 2026 | 270 |
| April 27, 2026 | 271 |
| April 29, 2026 | 272 |
| May 13, 2026 | 273 |
| September 6, 2026 | 274 |
The last 90 days run behind its lifetime average, which is ordinary for a mature project.
Observed activity milestones: 100 around Oct 2025
The commit history reads vercel/components.build 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 vercel/components.build.
Notes on vercel/components.build
- How many stars does vercel/components.build have?
- GitHub currently reports 793 stars for vercel/components.build. 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 components.build?
- gitdebt observed about 1 public star actions for vercel/components.build 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 components.build still active?
- Public archive data shows about 1 star actions for vercel/components.build in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
- When was components.build created?
- vercel/components.build was created on September 18, 2025. The first public star activity observed for vercel/components.build is from Oct 2025.
Read components.build 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/vercel/components.build?ref=readme">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/vercel/components.build/chart.svg?theme=dark" />
<img alt="vercel/components.build star history" src="https://api.gitdebt.com/api/repos/vercel/components.build/chart.svg?theme=light" />
</picture>
</a>
<sub>Star history source: Historical star data · Covers through September 6, 2026 · Still updating — <a href="https://gitdebt.com/vercel/components.build?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.