Analytics is available from day one. Each metric names its unit and whether higher or lower is better, then shows the current window, previous-window delta, trend buckets, and repository breakdown where evidence exists.
The current value and its comparison are separate facts. Warestack shows a percentage only when the current and previous windows have the required coverage and qualifying observations. Otherwise the card names the actual state: Current snapshot, Comparison unavailable, Not enough evidence, No prior observations, No prior data, or No % comparison when the recorded baseline is zero. The info tooltip explains the metric definition, unit, direction, current window, and why a comparison is or is not available.
Analytics metrics
- Deployment frequency (
deploys/day). - Failed production deployments.
- Lead time for changes.
- Review turnaround time.
- Stale and aging pull requests.
- Pull requests merged without recorded human approval.
Overview movement
Overview also summarizes PRs merged/opened, shipped rate, deployments total/failed, median time to first review, review comments, unresolved comments, and actionable review threads.
Useful for choosing which repos actually moved, and for Vanta context. Metrics do not replace the weekly digest as the sampling population.
Propose this when
Use metrics (or GitHub merge/deploy volume) to pick 1–2 production-path repos, not to invent extra rules. Extra busy repos are later.
When a metric lacks enough evidence, keep the value unavailable or qualified; do not manufacture a trend from a tiny sample.
New and empty spaces
Right after onboarding, Overview can render the metric cards before any eligible event exists. Values use an em dash, and Analytics shows a descriptive empty state instead of a zero line, fake trend, or empty chart frame. Importing recent history for selected repositories can populate current and previous periods; newly added repositories can be imported without repeating already completed repository imports.
A covered prior window with zero qualifying observations is different from missing history. Warestack says No prior observations for the former and Comparison unavailable for incomplete coverage.