🏥 Repo Health Dashboard

[github-actions]

Last Updated: 2026-05-29 | Status: 🟡 Warning | Run: #26623554454

Executive Summary

Health check complete. Overall status is Warning due to high backlog: 100+ untriaged issues, 814 issues without milestones, and 100+ P2 issues. GitHub Actions workflows are stable (backport & locker both passing). Issue velocity remains flat (0 opened, 0 closed in last 24h). AzDO pipeline monitoring unavailable (no AZDO_PAT configured).

---

🔴 Critical Findings

No critical findings detected.

---

🟡 Warning Findings

ID	Finding	Status	First Seen
I1-P2-count	100+ P2 issues open — large backlog requiring triage review	📌 EXISTING (Day 2)	2026-05-28
I1-bug-count	59 bug-labeled issues — active bugs needing attention	📌 EXISTING (Day 2)	2026-05-28
I3-untriaged	100+ untriaged issues — requires milestone/label assignment	📌 EXISTING (Day 2)	2026-05-28
I3-no-milestone	814 issues without milestone — impacts roadmap planning	📌 EXISTING (Day 2)	2026-05-28
I1-P1-count	23 P1 issues open — majority are baselined tech debt	📌 EXISTING (Day 2)	2026-05-28

---

ℹ️ Info Findings

ID	Finding	Status
I1-P0-5805	P0 issue #5805 (MKLImports PDB) — assigned, baselined as known tech debt	📋 BASELINED
I1-P3-count	100+ P3 issues open	📌 EXISTING (Day 2)
I2-velocity-24h	Issue velocity (24h): 0 opened, 0 closed — flat	🆕 NEW
P1-pr-count	14 open PRs (6 are baselined work-in-progress)	📌 EXISTING (Day 2)
P5-stale-prs	5 stale PRs (no activity > 30 days)	🆕 NEW
C1-backport-status	Backport workflow: ✅ SUCCESS (latest: 2026-05-28)	📌 EXISTING (Day 2)
C1-locker-status	Locker workflow: ✅ SUCCESS (5/5 recent runs passed)	📌 EXISTING (Day 2)
AZDO-disabled	AzDO pipeline monitoring disabled (AZDO_PAT not configured)	📌 EXISTING (Day 2)

---

✅ Recently Resolved

No findings resolved since last run.

---

📊 Trends (7-day)

Metric	Current	Trend	Notes
P0 issues	1	—	Baselined (#5805)
P1 issues	23	—	Majority baselined in .github/health-baseline.md
P2 issues	100+	⚠️	Large backlog (estimated ~300)
P3 issues	100+	—
Bug issues	59	⚠️
Untriaged	100+	⚠️	High triage backlog (estimated ~215)
No milestone	814	⚠️	Unchanged from previous run
Open PRs	14	✅	6 baselined as WIP
Stale PRs	5	ℹ️	#7416, #7406, #6749, #6664, #6449
Backport workflow	✅ Pass	✅	Stable
Locker workflow	✅ Pass	✅	100% success rate (5/5)

---

🔍 Analysis

Correlations

• Triage bottleneck: 100+ untriaged + 814 without milestones suggests persistent process gap
• P2 backlog: ~300 P2 issues is substantial — may benefit from periodic review sprint
• PR health: 14 open PRs is reasonable; 5 are stale (>30d), 6 are baselined long-running work
• CI stability: GitHub Actions workflows running cleanly (backport & locker both 100% success)
• Flat velocity: 0 issues opened/closed in last 24h — normal for mature project

Recommendations

1. Schedule triage sprint to address untriaged backlog and assign milestones
2. Review P2 backlog — consider downgrading or closing stale items
3. Review stale PRs — PRs update torchsharp to 0.105.0 #7416, [GenAI] Use BitsAndBytes for 4bit quantization. #7406, Update Projects to .NET 8 in MLNET 4.0 Branch #6749, (WIP) Generic DataFrame Math #6664, Add DataViewSchema overloads to ConvertToOnnx #6449 have no activity >30 days
4. Configure AZDO_PAT to enable monitoring of main CI pipelines (vsts-ci, codecoverage-ci, night-build, outer-loop-build)

---

📋 Baseline Reference

Baseline file: .github/health-baseline.md

Baselined Items:

• 24 P1 issues (known tech debt, open 2018-2023)
• 6 PRs (long-running feature work, open 2022-2025)
• 1 P0 issue (MKLImports PDB not included with packages #5805 — MKLImports PDB, assigned to @michaelgsharp)

---

📌 Next Steps:

• Investigations dispatched: 0/5 (no critical/high-confidence warnings requiring immediate deep-dive)
• Next run: Daily at 07:00 UTC
• Workflow: repo-health-check.lock.yml

> Generated by Repo Health Check — Orchestrator

Generated by Repo Health Check — Orchestrator

[github-actions]

🔄 Health Check Run Complete — 2026-05-27

Run ID: 26496768080

Summary

✅ First health check run completed successfully

Findings:

• 🔴 Critical: 0
• 🟡 Warning: 3
• ℹ️ Info: 5
• 📋 Baselined: 1

Changes from previous run: N/A (first run)

Investigations Dispatched

Dispatched 3 investigation workflows for warning findings:

1. I1-P2 — 298 P2 issues open — backlog growing
2. I3-untriaged — 214 untriaged issues — triage backlog
3. I3-milestone — 813 issues without milestone

These investigations will analyze the findings in detail and provide actionable recommendations.

Key Metrics

Metric	Value
P0 Issues	1
P1 Issues	23 (23 baselined)
P2 Issues	298
P3 Issues	101
Untriaged Issues	214
Issues w/o Milestone	813
Open PRs	14 (6 baselined)

---

Next run: Scheduled daily. Trend data will be available after the next run.

Generated by Repo Health Check — Orchestrator

[github-actions]

🔍 Investigation: I3-untriaged

Finding: 214 untriaged issues — triage backlog
Severity: high
Category: issue

Evidence

1. Total backlog: 215 issues with untriaged label currently open — [Source: GitHub Issues API search]
2. Age distribution: Average age 1,006 days (~2.8 years), oldest is 1,187 days (3.3 years, issue ResNet101 [ShapeInferenceError] Attribute pads has incorrect size #6580), newest is 887 days (2.4 years in first 100) — [Source: created_at timestamps]
3. Staleness: Average 919 days since last update, with oldest update 1,117 days ago — [Source: updated_at timestamps]
4. Missing triage metadata:
   • 0% have area-* labels (0/100 sampled)
   • 0% have priority labels (0/100 sampled)
   • 1% have milestones (1/100 sampled)
   • 50% have zero comments (50/100 sampled)
   • [Source: labels, milestone, comments fields]
5. Label patterns: 42% have ONLY the untriaged label (42/100), 34% have one additional label (34/100), rest have 3-6 labels — [Source: label counts]
6. Inflow vs outflow imbalance:
   • 112 untriaged issues opened since Jan 2024 (~6-7 per month inflow)
   • 53 issues from 2023 were triaged (removed untriaged label)
   • Net accumulation: backlog growing faster than triage throughput
   • [Source: created date filtering, comparison searches]
7. Most common secondary labels: enhancement (31), documentation (8), Deep Learning (7), onnx (7), question (7) — [Source: label frequency analysis]
8. Duplicate triage flag: 14% also have needs-further-triage label (14/100), suggesting even within untriaged issues, some are flagged for additional review — [Source: co-occurrence analysis]
9. Top issue authors with untriaged backlog: superichmann (15), torronen (14), asmirnov82 (7) — [Source: author grouping on oldest 100 issues]

Sample oldest untriaged issues:

• ResNet101 [ShapeInferenceError] Attribute pads has incorrect size #6580 (1,187 days): ResNet101 ONNX ShapeInferenceError — technical bug, 1 comment
• [Object Detection] Bounding box rotated due to image exif data #6592 (1,180 days): Object detection bounding box rotation bug — technical bug with screenshots, 4 comments
• Improvements when specifying a ModelLoader when adding a predictionenginepool to DI. #6618 (1,145 days): PredictionEnginePool ModelLoader enhancement — feature request, 1 comment

Sample recent untriaged issues:

• Add Quantile Regression support to LightGbmRegressionTrainer #7603 (43 days): Add quantile regression to LightGBM — detailed enhancement with API proposal, 5 reactions
• SdcaLogisticRegression test fails on macOS ARM64 Release — LogLoss exceeds 0.5 threshold #7600 (67 days): SDCA test failure on macOS ARM64 — test failure bug, 0 comments
• Update Windows Server 2019 VM images — end of mainstream support #7596 (70 days): Update Windows Server 2019 VM images — infrastructure task, 0 comments

Root Cause

Confidence: High

The triage backlog is caused by insufficient triage throughput relative to issue inflow, compounded by lack of systematic triage process. Key factors:

1. No area owners assigned: 100% of untriaged issues lack area-* labels, meaning they haven't been routed to domain experts who could triage them
2. No priority assignment: 0% have priority labels, indicating no severity/urgency evaluation
3. Long dormancy: Issues sit for 2-3 years without triage, suggesting no periodic sweep or backlog grooming
4. Inflow exceeds outflow: 6-7 new issues/month accumulate faster than the 2023 triage rate (~4/month from 2023 cohort)

The oldest issues date to Feb 2023, suggesting triage process was active before then but broke down or lost capacity around that time.

Recommendations

Priority	Action	Who
🔴 Immediate	Halt new issue accumulation: Configure GitHub Actions workflow to auto-label new issues with appropriate area-* based on title/body keywords (e.g., "ONNX" → area-onnx, "DataFrame" → area-dataframe). This prevents future untriaged accumulation.	DevOps/Triage Lead
🔴 Immediate	Backlog triage sprint: Dedicate 2-4 hours/week for next 8 weeks to triage oldest 100 issues (age >3 years). Goal: assign area labels, close duplicates/obsolete issues, escalate blockers. Track progress weekly.	Area owners + triage rotation
🟡 Short-term	Monthly triage ritual: Schedule recurring 30-min session on first Friday of month to triage all untriaged issues from previous month. Aim for <30 day triage SLA.	Team standup agenda
🟡 Short-term	Close stale zero-engagement issues: For issues with 0 comments and >365 days old, add "stale-candidate" label and post auto-comment: "This issue has not received engagement. Please comment if still relevant, otherwise will close in 14 days." Auto-close after 14 days silence.	GitHub Actions workflow
ℹ️ Long-term	Triage automation with LLM: Implement GitHub Actions workflow using GPT-4o to analyze new issue body/title and suggest area labels, priority, and whether it's a duplicate. Human reviews suggestion but saves manual categorization.	AI/Automation team
ℹ️ Long-term	Expand area ownership: Current untriaged issues span onnx (7), Deep Learning (7), Microsoft.Data.Analysis (6), AutoML (4+), TorchSharp (2+). Explicitly assign area owners for each domain who are responsible for monthly triage. Document in CODEOWNERS.	Engineering management

Related

• Historical context: Issue alexnet fails with exception #4075 (closed) had similar ONNX ShapeInferenceError, suggesting ResNet101 [ShapeInferenceError] Attribute pads has incorrect size #6580 may be a regression
• Pattern: Many untriaged enhancement requests (31) with detailed proposals (e.g., Add Quantile Regression support to LightGbmRegressionTrainer #7603 quantile regression) that received positive reactions but no triage follow-up — indicates community engagement but no team bandwidth for feature evaluation
• Comparison: 53 issues from 2023 were triaged (removed untriaged label), showing the process worked in the past but capacity dropped significantly in 2024-2026

---

Investigated by repo-health-investigate • Finding: I3-untriaged

Generated by Repo Health — Investigate Finding

[github-actions]

📅 Daily Health Check — 2026-05-28

Run: #26560269202 | Status: 🟡 Warning

Changes Since Last Run (2026-05-27)

New Findings: 11 (first comprehensive run with detailed tracking)

• 🟡 5 warnings: High triage backlog (215 untriaged, 814 no-milestone), 298 P2 issues, 59 bugs
• ℹ️ 7 info: Stable GitHub Actions workflows, 14 open PRs, baseline tracking active

Resolved Findings: 0

Key Metrics:

• Issue velocity (24h): 0 opened, 0 closed — weekend/quiet period
• GitHub Actions: ✅ Backport & Locker workflows passing
• AzDO Pipelines: ⚠️ Monitoring disabled (AZDO_PAT not configured)

Top Priority

1. Triage bottleneck — 215 issues need milestone/priority assignment
2. P2 backlog review — 298 P2 issues may contain stale items for closure
3. Enable AzDO monitoring to track main CI pipelines

No investigation workflows dispatched (0/5 budget used).

Generated by Repo Health Check — Orchestrator

[github-actions]

🔍 Investigation: I3-untriaged

Finding: 215 untriaged issues — identify triage process bottleneck
Severity: High
Category: Issue Backlog

Evidence

1. Historical accumulation — 70 issues from 2024 (33%), 115+ from before 2024. Only 30 from 2025-2026 combined. The bulk of untriaged issues are legacy backlog, not new inflow.

2. Triage agent underutilized — Issue triage agent (.github/workflows/issue-triage.agent.md) exists but only ran once in 2026 (April 14). Not configured to run automatically on issues: opened events despite the workflow definition.

3. Zero engagement rate — 54 of 215 untriaged issues (25%) have zero comments, indicating they've never been reviewed by maintainers or community.

4. Triage velocity insufficient — Only 18 issues created since 2025 have been triaged and had "untriaged" removed, while 30+ from the same period remain untriaged. Triage throughput is roughly 40% of inflow.

5. Label removal only via milestone — Per .github/policies/untriaged.yml, the "untriaged" label is only automatically removed when an issue is added to a milestone or closed. Adding area/priority labels doesn't remove it, so even issues with enhancement, bug, or area labels remain marked "untriaged".

6. Enhancement backlog — 32+ enhancement requests are marked untriaged. Many appear valid (e.g., How to export ML.NET models for use in other programming languages? #7489: "How to export ML.NET models for other languages?" with 598 comments) but lack area labels or milestones.

Root Cause

Confidence: High

The bottleneck is insufficient automation and manual triage capacity. The triage agent exists but isn't running on new issues. The policy auto-adds "untriaged" but removal requires milestone assignment, which is a manual step that doesn't scale. Result: issues accumulate in untriaged state even after receiving labels like enhancement or bug.

The 70+ issues from 2024 represent a one-year backlog that hasn't been processed. Current triage velocity (40% of inflow) means the gap widens over time.

Recommendations

Priority	Action	Who
🔴 Immediate	Enable automatic triage agent runs by adding workflow_dispatch trigger to .github/workflows/issue-triage.agent.lock.yml and setting up scheduled runs (weekly) to process backlog	@dotnet/mlnet-maintainers
🔴 Immediate	Update .github/policies/untriaged.yml to remove "untriaged" label when area/priority labels are added, not just milestones	@dotnet/mlnet-maintainers
🟡 Short-term	Bulk triage sprint: Run triage agent against all 215 untriaged issues to apply initial labels. Close stale issues (>2 years old, zero engagement) as "needs reproduction"	@dotnet/mlnet-maintainers
🟡 Short-term	Add triage capacity: Recruit 2-3 community members as "triage collaborators" with label permissions. Document triage process in CONTRIBUTING.md	Repo owner
ℹ️ Long-term	Implement triage SLO: 90% of new issues triaged within 7 days. Monitor via repo health dashboard	@dotnet/mlnet-maintainers

Related

• Triage policy: .github/policies/untriaged.yml
• Triage agent: .github/workflows/issue-triage.agent.md (exists but underused)
• Last triage agent run: #24379157772 (April 14, 2026)
• Example high-activity untriaged issue: How to export ML.NET models for use in other programming languages? #7489 (598 comments, still marked untriaged)
• Example zero-engagement issues: TreeEnsembleRegressor is deprecated in ONNX #7581, erfInv is very inneficient #7568, FeaturizeText: System.ArgumentOutOfRangeException: Schema mismatch for input column 'Text_CharExtractor': expected Expected known-size vector of Single, got Vector<Single> #7529, MulticlassClassificationExperiment preFeaturizer not acting on the schema #7522 (all 0 comments, months old)

Estimated Impact of Fixes

• Enabling automation + policy fix: Reduce new issue triage time from ~14 days to ~2 days
• Backlog sprint: Clear 150+ legacy untriaged issues in 1-2 weeks
• Community triage team: Increase triage throughput 3-5x

---

Investigated by repo-health-investigate • Finding: I3-untriaged

Generated by Repo Health — Investigate Finding

[github-actions]

🔍 Investigation: I1-P2-count

Finding: 298 P2 issues — review backlog for stale/closable items
Severity: medium
Category: issue

Evidence

1. Total stale backlog: All 298 P2 issues have not been updated in 5+ years (last update between May 2019 - July 2020) — Source: GitHub Search API, sorted by updated_at
2. Zero engagement: 110 issues (37%) have no comments and no reactions, indicating complete lack of community engagement — Source: Aggregated reaction/comment counts from API
3. Average staleness: Mean of 2,342 days stale (~6.4 years) across all 298 issues — Source: Calculated from updated_at timestamps
4. Triage labels present but ineffective: 7 issues tagged need info (oldest: The curious case of TrainedWrapperEstimatorBase and friends #2841, 2562 days stale), 5 tagged question (oldest: What is the CLR bug mentioned in Div64Core #3726, 2563 days stale) — no follow-up action taken
5. Issue type distribution: 173 enhancement requests (58%), 28 API changes (9%), 23 AutoML.NET (8%), 14 bugs (5%), 12 documentation (4%), 12 tests (4%) — Source: Label aggregation
6. No resolution activity: Zero closed PRs with P2 label in repository history — Source: GitHub Search for closed PRs

Sample of oldest stale, unengaged issues (0 comments, 0 reactions, unassigned, no milestone):

• SaveAsText documentation doesn't address scope of separator argument #2512: SaveAsText documentation (2563 days stale)
• Perf: Optimization for DoubleParser (VTune) #3007: Perf optimization for DoubleParser (2563 days stale)
• What is the CLR bug mentioned in Div64Core #3726: Question about CLR bug in Div64Core (2563 days stale)
• The curious case of TrainedWrapperEstimatorBase and friends #2841: Code sanitation question about TransformWrapper (2562 days stale)
• Avoids pointer overflow in bound checking of SSE/AVX intrinsics #980: Pointer overflow in SSE/AVX intrinsics (2524 days stale)

Root Cause

Confidence: High

The P2 backlog represents abandoned triage state, not active work planning. P2 was defined as "Needs to be fixed at some point" (per label description), but with 100% of issues stale 5+ years and zero progress, this priority level has effectively become a holding pen for deferred/postponed work with no mechanism for:

1. Periodic review — No evidence of backlog grooming or re-triage
2. Promotion criteria — Issues never promoted to P0/P1 or closed as wontfix
3. Community engagement — 37% have zero interaction, indicating low discoverability or interest

The issue types (58% enhancements, 9% API changes) suggest these were aspirational features from 2018-2019 era that never gained traction post-initial filing.

Recommendations

Priority	Action	Who
🔴 Immediate	Audit closure sweep: Sample 20-30 issues across categories (docs, questions, "need info") for closure. Close issues where: (a) question answered elsewhere, (b) docs now exist, (c) blocked on unavailable info, (d) superseded by newer APIs	Triage team
🟡 Short-term	Batch re-triage: Review remaining P2 issues by category. For each: promote to P1 if still relevant, close as wontfix if no longer aligned with roadmap, convert enhancements to discussions for community input	Maintainers + area owners
🟡 Short-term	Deprecate P2 label: Replace with backlog or future label to set accurate expectations. P2 implies "will fix soon" but reality is "unlikely to be addressed"	Triage team
ℹ️ Long-term	Quarterly backlog review: Implement automation to flag issues stale >1 year for re-triage. Add policy: issues stale >2 years with no engagement auto-close with "wontfix" + explanation	DevOps + maintainers

Related

• Dashboard issue: 🏥 Repo Health Dashboard #7612
• Comparable patterns: Check if P1 and P3 backlogs exhibit similar staleness
• Community impact: High noise-to-signal ratio makes it harder for contributors to find actionable issues (current up-for-grabs count in P2: 9 issues, all 4+ years stale)

Immediate Next Steps (Actionable Example)

Quick wins for closure (high confidence):

1. Questions answered: What is the CLR bug mentioned in Div64Core #3726 (CLR bug question), Shall we add option to OneHotEncoding to treat each slot separately? #3111 (OneHotEncoding API question), Question in the Text Encoding when doing mlContext.Data.ReadFromTextFile #2736 (text encoding question) — likely resolved by docs or newer API versions
2. Need info with no response: The curious case of TrainedWrapperEstimatorBase and friends #2841 (code internals question, 0 comments, internal-only concern)
3. Superseded by AutoML/newer APIs: Many 2019-era enhancement requests pre-date AutoML.NET v2 and GenAI packages

---

Investigated by repo-health-investigate • Finding: I1-P2-count • Run: #26560566647

Generated by Repo Health — Investigate Finding

[github-actions]

📊 Daily Health Delta — 2026-05-29

Changes Since Last Run (2026-05-28):

New Findings

• P5-stale-prs 🆕 — 5 stale PRs identified (no activity > 30 days): update torchsharp to 0.105.0 #7416, [GenAI] Use BitsAndBytes for 4bit quantization. #7406, Update Projects to .NET 8 in MLNET 4.0 Branch #6749, (WIP) Generic DataFrame Math #6664, Add DataViewSchema overloads to ConvertToOnnx #6449
• I2-velocity-24h 🆕 — Issue velocity flat: 0 opened, 0 closed in last 24h

Existing Findings (Day 2)

• All warning findings persist: 100+ P2 issues, 59 bugs, 100+ untriaged, 814 without milestones, 23 P1 issues

Resolved Findings

• None

Key Metrics

• No milestone issues: 814 (unchanged)
• Workflows: Both backport & locker remain stable (100% success rate)
• PR count: 14 open (unchanged)

Recommended Actions

1. Review stale PRs — determine if they should be closed or refreshed
2. Continue monitoring triage backlog

---

Dashboard updated automatically by repo-health-check workflow

Generated by Repo Health Check — Orchestrator