How many stars does k3s-io/vagrant-k3s have?
GitHub currently reports 41 stars for k3s-io/vagrant-k3s. The chart separately represents 32 public star actions and can differ because public WatchEvents do not include unstars.
Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.
coverage through Jul 2025
Hand a coding agent one prompt and it adds the star-history chart, a stars-and-forks badge, and whichever repo-health charts fit tok3s-io/vagrant-k3s's README — light and dark variants, alt text, and the measured numbers already filled in.
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.
Embeddable maintenance, ownership, and star-momentum signals, computed from commit and star history.
Fix-labelled changes, file change frequency, ownership risk, and maintenance cadence for k3s-io/vagrant-k3s, each computed from its analyzed commit window.
No published package detected for this repo — nothing to overlay against star growth.
GitHub currently reports 41 stars for k3s-io/vagrant-k3s. The chart separately represents 32 public star actions and can differ because public WatchEvents do not include unstars.
gitdebt observed about 2 public star actions for k3s-io/vagrant-k3s 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 in line with its lifetime average activity pace.
Public archive data shows about 1 star actions for k3s-io/vagrant-k3s in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
k3s-io/vagrant-k3s was created on October 4, 2021. The first public star activity observed for k3s-io/vagrant-k3s is from Oct 2021.