β 2026-03-04
Overall: π΄ UNHEALTHY
Status: π΄ 4 critical Β· π‘ 8 warnings Β· π΅ 3 info
This is the first comprehensive health check of the ML.NET repository. The analysis reveals several critical issues requiring immediate attention: a massive untriaged backlog of 211 issues, 1 open P0 issue from 2021, and 3 community PRs that have been waiting 2-3 years for review. However, CI health is strong with 100% GitHub Actions pass rate over the last 7 days.
π¨ Maintainer Action Required
Immediate (π΄ Critical)
- π₯ P0 Issue: #5805 - MKLImports PDB not included with packages (assigned:
@michaelgsharp, age: 1745 days / 4.8 years)
- π₯ Massive Untriaged Backlog: 211 untriaged issues - this is a critical triage bandwidth problem
- Most recent: #7581 - TreeEnsembleRegressor is deprecated in ONNX (Feb 17)
- Only 1 new untriaged issue in last 7 days (low intake but huge backlog)
- π₯ CI Stability: 16 open
blocking-clean-ci issues indicate ongoing build reliability problems
- #7419, #7418, #7417, #7393, #7343, #7067, #7060, #7057, #6996, #6978, #6971, #6961, #6960, #6843, #6842, #6841
- π₯ Ancient Community PRs: 3 community contribution PRs have been waiting 2-3+ years without review
- #6253 - Add Generic ColumnName Type (1329 days / 3.6 years)
- #6449 - Add DataViewSchema overloads to ConvertToOnnx (1209 days / 3.3 years)
- #6451 - Adds type forwarding attributes for types moved from Microsoft.ML.TimeSeries (1206 days / 3.3 years)
Timely (π‘ Warning)
- P1 Issues: 23 open P1 issues, including:
- #7447 - Legacy images need to be updated (assigned:
@michaelgsharp)
- #6588 - Error when target runtime is linux-arm/arm64 (assigned:
@michaelgsharp)
- #6370 - Exposing the tree for multiclass classification (assigned:
@michaelgsharp)
- 20 more P1 issues...
- Unanswered Questions: 52 question issues remain open with no answers, with oldest from 2018
- #181 - Reinforcement learning (created: May 2018, 2848 days old)
- #512 - Make grid search of parameter space more efficient (created: Jul 2018)
- 50 more unanswered questions...
- Open Bugs: 58 open bug issues need review and triage
- Known Build Errors: 16 open
Known Build Error issues
- Stale PRs: 4 PRs open for over 1 year, including #6943 (838 days)
π¬ Pending Community Interactions
Items where a community member is waiting for a maintainer response.
| # |
Title |
Type |
Author |
Waiting Since |
Last Activity |
| #181 |
Reinforcement learning |
Question |
jarnmo |
May 2018 |
Jun 2018 (user) |
| #6253 |
Add Generic ColumnName Type |
PR |
StanleyGoldman |
Jul 2022 |
1329 days open |
| #6449 |
Add DataViewSchema overloads to ConvertToOnnx |
PR |
FranklinWhale |
Nov 2022 |
1209 days open |
| #6451 |
Adds type forwarding attributes |
PR |
Wraith2 |
Nov 2022 |
1206 days open |
| #7174 |
Add AutoEncoder as Feature Selection |
Issue |
superichmann |
Jul 2024 |
Feb 2025 (maintainer) |
Summary: 52 unanswered questions Β· 211 untriaged issues Β· 3 community PRs awaiting review (2-3 years old)
π§ CI / Workflow Health
GitHub Actions (7-day summary)
| Workflow |
Runs |
β
Pass |
β Fail |
βΉοΈ Cancel |
Rate |
| Backport PR to branch |
1 |
1 |
0 |
0 |
100.0% |
| Locker - Lock stale issues and PRs |
8 |
8 |
0 |
0 |
100.0% |
Status: β
All workflows passing - 100% success rate across all workflows in the last 7 days
Failed Runs (last 24h)
β
No failed runs in the last 24 hours
Cancelled Runs (last 24h)
β
No cancelled runs in the last 24 hours
Azure DevOps Status (Heuristic)
- Open
blocking-clean-ci issues: 16 π΄
- Open
Known Build Error issues: 16 π‘
Top blocking-clean-ci issues:
- #7419 - TestAppendMany_SizeMoreThanMaxBufferCapacity triggers OOM killer
- #7418 - AutoMLExperiment_return_current_best_trial_when_ct_is_canceled fails
- #7417 - Code coverage build fails to instrument file in use
- #7393 - Resource contention in tests DownloadImageSet
- #7343 - SdcaLogisticRegression failing on Apple M1
π Bug & Issue Landscape
| Metric |
Current |
7d Ago |
Ξ |
Trend |
| Open issues (total) |
N/A |
N/A |
β |
First run |
| Open bugs |
58 |
N/A |
β |
First run |
| Untriaged issues |
211 |
N/A |
β |
First run |
| Open P0 |
1 |
β |
β |
β |
| Open P1 |
23 |
β |
β |
β |
| Issues opened (7d) |
0 |
β |
β |
β |
| Issues closed (7d) |
0 |
β |
β |
β |
High-Priority Bugs (P0/P1)
| # |
Title |
Priority |
Assignee |
Age (days) |
Milestone |
| #5805 |
MKLImports PDB not included with packages |
P0 |
@michaelgsharp |
1745 |
β |
| #7447 |
Legacy images need to be updated |
P1 |
@michaelgsharp |
314 |
β |
| #6588 |
Error: linux-arm/arm64 not supported |
P1 |
@michaelgsharp |
1098 |
β |
| #6370 |
Exposing the tree for multiclass classification |
P1 |
@michaelgsharp |
1240 |
β |
| #6353 |
CreateEnumerable code fails in VS FSI |
P1 |
unassigned |
1247 |
β |
| #5798 |
Add substitutes for 4 IntelMKL methods for ARM |
P1 |
unassigned |
1752 |
β |
| #5744 |
Memory leak |
P1 |
unassigned |
1787 |
β |
| #5587 |
Migrate to VSTest for all Unit Tests |
P1 |
unassigned |
1877 |
β |
| #5569 |
OMP Error in Image Classification with AutoML |
P1 |
unassigned |
1893 |
β |
| #5566 |
SVMLightLoader Fails above 128 dense rows |
P1 |
unassigned |
1899 |
β |
(showing 10 of 24 total P0/P1 issues)
π Security Issues
- #3604 - Ensure ML.NET models are treated as code in security docs (P3, documentation) - assigned to
@natke
π₯ Pull Request Status
| Metric |
Current |
7d Ago |
Ξ |
Trend |
| Open PRs |
12 |
N/A |
β |
First run |
| PRs merged (7d) |
0 |
β |
β |
β |
| Community PRs awaiting review |
3 |
β |
β |
β |
Open PRs Needing Attention
| # |
Title |
Author |
Age (days) |
Reviews |
Labels |
| #6253 |
Add Generic ColumnName Type |
StanleyGoldman |
1329 |
0 |
community-contribution |
| #6449 |
Add DataViewSchema overloads to ConvertToOnnx |
FranklinWhale |
1209 |
0 |
community-contribution |
| #6451 |
Adds type forwarding attributes |
Wraith2 |
1206 |
1 β
|
community-contribution |
| #6943 |
Bumped TorchSharp version to 0.98.3 |
artidoro |
838 |
0 |
β |
| #7436 |
Update DnnCatalog to remove deprecated transforms |
luisquintanilla |
331 |
0 |
β |
| #7231 |
Bump dependencies with warnings |
teo-tsirpanis |
216 |
0 |
β |
| #7213 |
Fix path of Native Dependencies |
ericstj |
238 |
0 |
β |
| #7200 |
Bump torchsharp to latest version |
xiaoyun94 |
257 |
0 |
test-error,onnx |
| #7181 |
Bump dependencies on license update |
teo-tsirpanis |
280 |
0 |
β |
Critical: 3 community PRs have been open for 2-3+ years without any review or feedback
π 7-Day Trends
| Metric |
Current |
Previous |
Ξ |
Trend |
| Issues opened/day |
0.0 |
N/A |
β |
First run |
| Issues closed/day |
0.0 |
N/A |
β |
First run |
| PRs merged/day |
0.0 |
N/A |
β |
First run |
| GH Actions pass rate |
100% |
N/A |
β |
First run |
π‘ Recommendations
-
Emergency Triage Sprint: The 211 untriaged issues represent a critical backlog. Dedicate focused time to batch-triage these issues, especially older ones that may no longer be relevant.
-
Community PR Immediate Action: The 3 community PRs that have been open for 2-3 years need immediate attention. Either review and merge, request changes, or close with explanation. This severely impacts community trust and contribution willingness.
-
P0 Issue Resolution: Issue #5805 (MKLImports PDB) has been assigned to @michaelgsharp since 2021. Either resolve or reassign if no longer actionable.
-
Question Cleanup Campaign: 52 unanswered questions (some from 2018) should be reviewed. Consider closing very old questions with a polite explanation if they're no longer relevant or cannot be answered.
-
CI Issue Review: The 16 blocking-clean-ci issues should be reviewed to determine which are actively blocking vs. historical. Consider closing resolved ones and prioritizing active blockers.
π Correlation Insights
-
Triage Bandwidth Crisis: The massive untriaged backlog (211 issues) combined with ancient unanswered questions (52 from 2018-present) and years-old community PRs suggests a severe maintainer bandwidth/prioritization issue rather than a technical problem.
-
CI Discrepancy: GitHub Actions shows 100% pass rate while 16 blocking-clean-ci issues are open. This suggests either (a) Azure DevOps pipelines have issues not reflected in GH Actions, (b) these issues are historical and no longer active, or (c) CI health has improved but issue cleanup hasn't happened.
-
Low Activity Period: Zero issues opened/closed and zero PRs merged in the last 7 days may indicate this is a low-activity period, possibly explaining why no recent CI failures occurred despite blocking issues.
-
Community Engagement Gap: The combination of 3 community PRs waiting 2-3 years, 211 untriaged issues, and 52 unanswered questions points to a systematic community engagement problem that needs organizational attention.
-
Priority vs. Reality: 24 P0/P1 issues open (including one P0 from 2021) while 211 issues remain untriaged suggests prioritization may not be effectively driving work allocation.
π€ Generated by ML.NET Repo Health Check Β· 2026-03-04T16:19:28Z UTC
Generated by ML.NET Repository Health Check
β 2026-03-04
Overall: π΄ UNHEALTHY
Status: π΄ 4 critical Β· π‘ 8 warnings Β· π΅ 3 info
π¨ Maintainer Action Required
Immediate (π΄ Critical)
@michaelgsharp, age: 1745 days / 4.8 years)blocking-clean-ciissues indicate ongoing build reliability problemsTimely (π‘ Warning)
@michaelgsharp)@michaelgsharp)@michaelgsharp)Known Build Errorissues㪠Pending Community Interactions
Summary: 52 unanswered questions Β· 211 untriaged issues Β· 3 community PRs awaiting review (2-3 years old)
π§ CI / Workflow Health
GitHub Actions (7-day summary)
Status: β All workflows passing - 100% success rate across all workflows in the last 7 days
Failed Runs (last 24h)
β No failed runs in the last 24 hours
Cancelled Runs (last 24h)
β No cancelled runs in the last 24 hours
Azure DevOps Status (Heuristic)
blocking-clean-ciissues: 16 π΄Known Build Errorissues: 16 π‘Top blocking-clean-ci issues:
π Bug & Issue Landscape
High-Priority Bugs (P0/P1)
@michaelgsharp@michaelgsharp@michaelgsharp@michaelgsharp(showing 10 of 24 total P0/P1 issues)
π Security Issues
@natkeπ₯ Pull Request Status
Open PRs Needing Attention
Critical: 3 community PRs have been open for 2-3+ years without any review or feedback
π 7-Day Trends
π‘ Recommendations
Emergency Triage Sprint: The 211 untriaged issues represent a critical backlog. Dedicate focused time to batch-triage these issues, especially older ones that may no longer be relevant.
Community PR Immediate Action: The 3 community PRs that have been open for 2-3 years need immediate attention. Either review and merge, request changes, or close with explanation. This severely impacts community trust and contribution willingness.
P0 Issue Resolution: Issue #5805 (MKLImports PDB) has been assigned to
@michaelgsharpsince 2021. Either resolve or reassign if no longer actionable.Question Cleanup Campaign: 52 unanswered questions (some from 2018) should be reviewed. Consider closing very old questions with a polite explanation if they're no longer relevant or cannot be answered.
CI Issue Review: The 16
blocking-clean-ciissues should be reviewed to determine which are actively blocking vs. historical. Consider closing resolved ones and prioritizing active blockers.π Correlation Insights
Triage Bandwidth Crisis: The massive untriaged backlog (211 issues) combined with ancient unanswered questions (52 from 2018-present) and years-old community PRs suggests a severe maintainer bandwidth/prioritization issue rather than a technical problem.
CI Discrepancy: GitHub Actions shows 100% pass rate while 16
blocking-clean-ciissues are open. This suggests either (a) Azure DevOps pipelines have issues not reflected in GH Actions, (b) these issues are historical and no longer active, or (c) CI health has improved but issue cleanup hasn't happened.Low Activity Period: Zero issues opened/closed and zero PRs merged in the last 7 days may indicate this is a low-activity period, possibly explaining why no recent CI failures occurred despite blocking issues.
Community Engagement Gap: The combination of 3 community PRs waiting 2-3 years, 211 untriaged issues, and 52 unanswered questions points to a systematic community engagement problem that needs organizational attention.
Priority vs. Reality: 24 P0/P1 issues open (including one P0 from 2021) while 211 issues remain untriaged suggests prioritization may not be effectively driving work allocation.
π€ Generated by ML.NET Repo Health Check Β· 2026-03-04T16:19:28Z UTC