🏥 Repo Health Dashboard

Last Updated: 2026-05-03 06:47 UTC | Status: ⚠️ CAUTION | Workflow: Run #25272281149

Executive Summary

ML.NET repo health requires attention: 216 untriaged issues and 298 P2 issues indicate significant backlog accumulation. Critical P0 issue #5805 has remained unresolved since 2021 (baselined but requires decision). CI/CD pipelines remain healthy with successful runs across backport and locker workflows.

🔴 Critical Findings (1 — BASELINED)

ID	Status	Summary	Details
I1-P0-5805	📋 BASELINED	P0 issue #5805 open for 5+ years (since 2021)	MKLImports PDB missing from packages. Assigned to @michaelgsharp. Baselined 2026-03-06 per health-baseline.md

🟡 Warnings (2 — NEW)

ID	Status	Summary	Age
I2-UNTRIAGED-216	🆕 NEW	216 untriaged issues requiring triage	Day 1
I3-P2-BACKLOG-298	🆕 NEW	298 P2 priority issues (medium backlog)	Day 1

ℹ️ Info (4)

ID	Status	Summary	Details
I4-P1-BASELINED-23	📋 BASELINED	23 P1 issues (22 baselined, technical debt)	Most from 2018-2021, known limitations/design decisions
PR1-SINGLE-OPEN	🆕 NEW	1 open PR (healthy velocity)	Low count suggests fast merge process
CI1-BACKPORT-HEALTHY	🆕 NEW	GitHub Actions backport.yml passing	Latest run: success
CI2-LOCKER-HEALTHY	🆕 NEW	GitHub Actions locker.yml passing	410 total runs, latest: success

✅ Recently Resolved (0)

Comparison with previous run (2026-05-02): Key metrics show minimal change. Untriaged count remained stable at 216 (previously tracked as 216). P0 issue #5805 remains baselined.

📊 Key Metrics

Issues:

• Total open: 639+ issues
• Priority breakdown: 1 P0 | 23 P1 | 298 P2 | 101 P3 | 59 Bug
• Untriaged: 216 issues ⚠️
• Oldest P0: MKLImports PDB not included with packages #5805 (1826 days old, opened 2021)

Pull Requests:

• Open: 1 PR ✅
• Velocity: Fast merge process indicated

CI/CD Health:

• GitHub Actions: ✅ All workflows passing (backport.yml, locker.yml)
• Azure DevOps: ⚠️ Monitoring disabled (no AZDO_PAT configured)

Baseline Tracking:

• Baselined issues: 24 items (P0 MKLImports PDB not included with packages #5805 + 23 P1 issues from 2018-2021)
• Baselined PRs: 6 items
• Last baseline review: 2026-03-06
• Next review due: 2026-04-05 (overdue)

🎯 Recommended Actions

High Priority

1. Triage Sprint: Process 216 untriaged issues — assign milestones and priority labels
2. P0 Decision: Issue MKLImports PDB not included with packages #5805 requires executive decision after 5+ years (fix, defer with timeline, or close)
3. Baseline Review: Overdue since 2026-04-05 — escalate items baselined >90 days per policy

Medium Priority

4. P2 Backlog Grooming: Review 298 P2 issues for prioritization and closure opportunities
5. AzDO Monitoring: Configure AZDO_PAT secret to enable Azure Pipeline health tracking (vsts-ci, codecoverage-ci, night-build, outer-loop-build)

📋 Detailed Findings

🔴 Critical: P0 Issue #5805 (BASELINED, 5 Years Old)

Issue: #5805 "MKLImports PDB not included with packages"

• Opened: May 2021 (1826 days ago)
• Status: Assigned to @michaelgsharp, no recent activity since June 2021
• Impact: Missing debug symbols for MKL native binaries
• Baseline status: Accepted as "Known packaging tech debt" on 2026-03-06
• Policy violation: Baselined item has not been resolved within 90 days → requires escalation

Action: Schedule executive review to determine: (1) commit resources to fix, (2) establish concrete timeline, or (3) officially accept as permanent limitation and document workaround.

🟡 Warning: 216 Untriaged Issues

Finding: Large backlog of issues marked untriaged requiring milestone and priority assignment.

Analysis: High untriaged count indicates either:

• High incoming issue velocity without matching triage capacity
• Process gap in automated triage or team triage cadence

Action:

• Schedule dedicated triage sessions to process backlog
• Consider automated triage rules for common issue types
• Review triage SLA and team capacity

🟡 Warning: 298 P2 Issues

Finding: Medium-priority backlog of 298 issues.

Analysis: P2 accumulation is normal for large repositories, but 298 represents significant deferred work. Combined with 23 P1 issues, total backlog of 321 priority issues suggests need for prioritization review.

Action:

• Quarterly backlog grooming to identify:
  • Items that can be closed (no longer relevant, duplicates)
  • Items that should be promoted to P1
  • Items that should be demoted to P3 or closed
• Consider milestone assignments to distribute work across releases

ℹ️ Info: Healthy CI/CD and Low PR Count

Positive signals:

• GitHub Actions workflows (backport, locker) show 100% success rate
• Only 1 open PR indicates either:
  • Fast PR review/merge velocity (positive)
  • Low development activity (context-dependent)

No action required — monitor trends over time.

---

Comparison with Baseline

The health-baseline.md file documents 24 baselined issues and 6 baselined PRs. All P1 issues found in current scan match the baseline list (items from 2018-2021 representing accepted technical debt and design decisions).

Baseline policy compliance:

• ✅ All baselined items are correctly classified
• ⚠️ Baseline review overdue (due 2026-04-05, currently 2026-05-03)
• ⚠️ P0 MKLImports PDB not included with packages #5805 baselined >90 days ago (baselined 2026-03-06, currently Day 58 since baseline)

---

Baseline: .github/health-baseline.md

Generated by Repo Health Check — Orchestrator

Generated by Repo Health Check — Orchestrator