What Periscope tracks
For each monitored repository, the dashboard shows:- Merge count — total PRs merged in the time period
- Contributor count — number of distinct contributors
- Average cycle time — mean PR cycle time (in hours)
- Health status — healthy, warning, or stale
- Last merge date — when the most recent PR was merged
- Weekly sparkline — visual trend of merge activity
Health classification
| Status | Criteria |
|---|---|
| Healthy | Regular merge activity, multiple contributors, reasonable cycle times |
| Warning | Reduced activity, single contributor, or elevated cycle times |
| Stale | No merge activity in 14+ days |
How it is calculated
Periscope queries all merged PRs for each repository in the selected time range and computes:- Total merges and distinct authors
- Average cycle time across all PRs
- Recency of the most recent merge
- Weekly merge counts for the sparkline
Interpreting the data
Stale services
A stale repository is not necessarily a problem. It may be:- A mature, stable service that rarely changes
- A deprecated service that should be decommissioned
- A service that has been abandoned and needs ownership
Single-contributor services
Services with only one contributor are a bus factor risk. If that person leaves or is unavailable, the team has no one who understands the codebase. Periscope flags this as a risk signal.Cycle time outliers
A service with much higher cycle time than others may have:- More complex code that takes longer to review
- Fewer reviewers available (related to bus factor)
- A slower CI pipeline specific to that repository