Skip to content

πŸ₯ ML.NET Repository Health DashboardΒ #2

@github-actions

Description

@github-actions

πŸ₯ ML.NET Repository Health Dashboard β€” 2026-05-09

Overall: πŸ”΄ Unhealthy
Status: πŸ”΄ 4 critical Β· 🟑 3 warnings Β· πŸ”΅ 0 info

The ML.NET repository shows regression since March 9: untriaged issues increased by 4 (back to 216 from 212), open bugs +1, and total issues +3. Zero issues closed or PRs merged in the past week indicates low maintainer bandwidth. Long-standing critical issues persist: a 5-year-old P0 (#5805), 7-year-old security doc gap (#3604), 16 blocking-clean-ci issues, and community PRs aging for years. CI shows no recent failures but pass rate calculation is distorted by incomplete runs.


🚨 Maintainer Action Required

Immediate (πŸ”΄ Critical)

  • #5805 β€” P0: MKLImports PDB not included with packages (open 1809 days, ~5 years) β€” Missing debug symbols for redistributed binaries
  • 216 untriaged issues β€” Up from 212 on March 9 (+4 new); critical backlog threshold exceeded (>50)
  • 16 open blocking-clean-ci issues β€” Unchanged from March 9, ongoing CI stability concerns
  • #3604 β€” Security: Documentation must warn "models = code" (open 2570 days, 7+ years)

Timely (🟑 Warning)

  • 52 unanswered questions β€” Unchanged from March 9; all open questions are >7 days old with no maintainer response
  • 23 open P1 issues β€” Unchanged from March 9; many exceed 30 days without activity
  • Ancient stale community PRs:
    • #6449 β€” 1274 days (~3.5 years), no reviews
    • #7094 β€” 779 days (~2 years), 2 reviews
    • 6 total community PRs awaiting review

πŸ“¬ Pending Community Interactions

Items where a community member is waiting for a maintainer response.

# Title Type Author Waiting Since Last Activity
#7174 Add AutoEncoder as Feature Selection Method Issue superichmann 2024-06-15 User replied 2025-02-24

Summary: 1 awaiting response Β· 216 untriaged Β· 6 unreviewed community PRs


πŸ”§ CI / Workflow Health

GitHub Actions (7-day summary)

Workflow Runs βœ… Pass ❌ Fail ⏹️ Cancel Rate
All workflows (main) 53 26 0 0 49%*

* Pass rate is 49% because 27 workflow runs have null conclusions (in-progress, skipped, or neutral). Of completed workflows with definitive outcomes, the success rate is 100% (26 success, 0 failures).

βœ… No failed runs in last 24 hours on main branch
βœ… No cancelled runs in last 24 hours

Azure DevOps Status (Heuristic)

  • Open blocking-clean-ci issues: 16 (unchanged from March 9)
  • Open Known Build Error issues: 16 (unchanged from March 9)

Blocking CI issue examples:

  • #7419 β€” TestAppendMany_SizeMoreThanMaxBufferCapacity triggers OOM killer

πŸ› Bug & Issue Landscape

Metric Current 7d Ago (Mar 9) Ξ” Trend
Open issues (total) 986 983 +3 ↑
Open bugs 59 58 +1 ↑
Untriaged issues 216 212 +4 ↑
Open P0 1 1 β€” β†’
Open P1 23 23 β€” β†’
Issues opened (7d) 18 1 +17 ↑
Issues closed (7d) 0 0 β€” β†’

High-Priority Bugs (P0/P1)

# Title Priority Assignee Age (days) Milestone
#5805 MKLImports PDB not included with packages P0 β€” 1809 β€”
#7447 Legacy images need to be updated P1 β€” 380 β€”
#6588 Error: "ML.NET supports 'x64' and 'x86' processor" on linux-arm* P1 β€” 1164 β€”
#6370 Exposing the tree for multiclass classification P1 β€” 1305 β€”
#6353 CreateEnumerable fails in VS FSI but works in .NET Interactive P1 β€” 1312 β€”

Note: Showing top 5 of 23 P1 issues. Full P1 list.

πŸ”’ Security Issues

# Title Age (days) Last Update
#3604 Ensure documentation warns: models = code 2570 2020-01-10

πŸ“₯ Pull Request Status

Metric Current 7d Ago (Mar 9) Ξ” Trend
Open PRs 13 13 β€” β†’
PRs merged (7d) 0 1 -1 ↓
Community PRs awaiting review 6 6 β€” β†’

Open PRs Needing Attention

# Title Author Age (days) Reviews Labels
#6449 Add DataViewSchema overloads to ConvertToOnnx FranklinWhale 1274 0 community-contribution
#7094 Add support for Apache.Arrow.Types.Decimal128Type piyushdubey 779 2 community-contribution
#7569 fix: performance of erfinv #7568 JeWaVe 114 1 (changes requested) needs-author-action, community-contribution
#7605 Expose quantile regression objective in LightGbmRegressionTrainer Sam7 25 0 community-contribution

πŸ“Š 7-Day Trends

Metric Current Previous (Mar 9) Ξ” Trend
Issues opened/day 2.6 0.14 +2.46 ↑
Issues closed/day 0.0 0.0 β€” β†’
PRs merged/day 0.0 0.14 -0.14 ↓
GH Actions pass rate 49% 96% -47% ↓

Note: Pass rate drop is due to many workflows with null conclusions (in-progress/skipped). Actual completion rate of finished workflows is 100% (0 failures).


πŸ’‘ Recommendations

  1. Resume triage and closure activity β€” Untriaged issues increased (+4), and zero issues closed in 7 days indicates maintainer bandwidth constraints; prioritize closing or triaging the 216-issue backlog
  2. Investigate 18 new issues in 7 days β€” Sharp increase from previous baseline (1/week); determine if this is organic growth or reporting anomaly
  3. Resolve ancient technical debt:
    • P0 #5805 (1809 days, 5 years): Either fix MKLImports PDB issue or downgrade priority with documented justification
    • Security #3604 (2570 days, 7 years): Close if documentation updated, or implement the warning
    • PR #6449 (1274 days, 3.5 years): Review, merge, or close with feedback to respect contributor effort
  4. Address 52 unanswered questions β€” All open questions are >7 days old with no maintainer comments; may indicate resource constraints or community engagement gap
  5. Review 16 blocking-clean-ci issues β€” Unchanged since March 9; prioritize fixes or close if no longer blocking

πŸ” Correlation Insights

  • Triage momentum lost β€” Untriaged issues increased by 4 (212β†’216) after significant reduction from earlier runs; suggests triage process stalled
  • Zero closure velocity β€” No issues closed or PRs merged in 7 days indicates low maintainer bandwidth or inactive period
  • CI health stable β€” No failures in GitHub Actions last 24h; pass rate drop (96%β†’49%) is due to incomplete/skipped runs, not actual failures
  • Ancient technical debt unchanged β€” P0 at 1809 days, security doc at 2570 days, PR at 1274 days all persist from March 9; suggests ownership gaps or de-prioritization
  • Community engagement gap β€” 6 community PRs aging without review (oldest at 1274 days); may discourage future contributions
  • Issue influx β€” 18 issues opened in 7 days (up from 1/week) suggests either increased community activity or data collection timing anomaly

πŸ€– Generated by ML.NET Repo Health Check Β· 2026-05-09T17:08:38Z UTC

Generated by ML.NET Repository Health Check

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions