Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.
coverage through Jun 2026
Observed activity milestones: 100 around Jun 20201k around Jun 2020
Hand a coding agent one prompt and it adds the star-history chart, a stars-and-forks badge, and whichever repo-health charts fit togoogle/tsunami-security-scanner'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 google/tsunami-security-scanner, each computed from its analyzed commit window.
No published package detected for this repo — nothing to overlay against star growth.
GitHub currently reports 8,596 stars for google/tsunami-security-scanner. The chart separately represents 8,877 public star actions and can differ because public WatchEvents do not include unstars.
gitdebt observed about 10 public star actions for google/tsunami-security-scanner over the latest 90 days of archive coverage (about 4 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.
Public archive data shows about 4 star actions for google/tsunami-security-scanner in the latest 30 days of coverage. For repository activity, use the commit heatmap, commit trend, and contributor charts on this page.
google/tsunami-security-scanner was created on June 3, 2020. The first public star activity observed for google/tsunami-security-scanner is from Jun 2020.