Team Analytics

The Analytics page gives you a cross-repo, org-wide view of your team's pull request activity and governance outcomes. Instead of looking at one repo at a time, you can see how risk scores, auto-merge rates, and approval workflows are performing across your entire organization.

Navigate to Dashboard → Analytics to access the page. You can filter all tabs by a time range — last 7 days, 30 days, 90 days, or the full year.

The Repos tab shows per-repository performance metrics:

• Total PRs — Number of pull requests in the period
• Avg Risk — Average risk score across all analyzed PRs
• High Risk — Count of PRs scoring 50 or above
• Auto-Merge Rate — Percentage of auto-merge decisions that resulted in a successful merge
• Top Agent — The most active AI agent in that repo

Use this tab to identify which repositories have the highest risk profiles and which ones benefit most from auto-merge. If a repo shows a low auto-merge rate, check its auto-merge configuration — the rules may be too strict.

The Team tab breaks down PR activity by author, distinguishing between human and agent/bot contributors:

• See which team members produce the most high-risk PRs
• Compare risk profiles between human developers and AI agents
• Identify authors who consistently produce low-risk changes

This data helps you understand whether AI agents are being used effectively and whether any contributors need additional review attention.

The Agents tab provides an org-wide comparison of all AI coding agents:

• PRs — Total PRs attributed to each agent
• Avg Risk — Average risk score of the agent's PRs
• Trust — Current trust score for the agent in your org
• Total Analyses — Number of completed analyses

Use this to compare how different agents perform. For example, you might find that Dependabot consistently produces low-risk dependency updates while a coding assistant occasionally generates higher-risk changes that need more review.

The Auto-Merge tab aggregates all auto-merge decisions across your org:

• Approved / Merged / Blocked / Failed — Breakdown of decision outcomes
• Top Block Reasons — The most common rules blocking auto-merge, displayed as a ranked bar chart

If you see a high blocked rate, review the Top Block Reasons to understand which rules are triggering most often. Common patterns:

• risk_score_too_high — Consider adjusting maxRiskScore or adding custom policies to reduce scores for safe patterns
• trust_level_too_low — New agents need more history; consider setting minTrustLevel to medium initially
• checks_not_passing — CI checks are failing independently of MergeShield

When no auto-merge decisions exist for the selected period, the tab shows a helpful message directing you to enable auto-merge on a repository.

The Approvals tab tracks approval workflow performance:

• Total Approvals — All approval requests in the period
• Pending / Approved / Rejected — Current status breakdown
• Avg Response — Average time from approval request to decision (in hours)

A high pending count may indicate that reviewers are not responding to escalation requests. Consider adjusting timeoutHours in your approval workflow settings, or adding more escalation reviewers.

A high average response time suggests your team may benefit from Slack notifications — install the Slack app to get real-time alerts when approvals are needed.

All analytics data is available via the REST API. Each tab corresponds to a dedicated endpoint:

• GET /api/analytics/repos?days=30
• GET /api/analytics/team?days=30
• GET /api/analytics/agents-org?days=30
• GET /api/analytics/auto-merge?days=30
• GET /api/analytics/approvals?days=30

You can also export PR data as CSV via GET /api/analytics/export. All endpoints accept a days query parameter (1–365) to control the time range.

Use these endpoints to build custom dashboards, generate reports, or integrate analytics into your team's existing tools.