Skip to content

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

Description

@github-actions

β€” 2026-03-04

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

First Run: This is the initial baseline health check for the dotnet/machinelearning repository. The repository shows several critical issues requiring immediate maintainer attention, particularly around untriaged issues (100 items), unanswered questions (52 items), CI health (16 blocking issues), and a long-standing P0 bug. Community engagement is low with 5 stale community PRs, including one open for over 3 years.


🚨 Maintainer Action Required

Immediate (πŸ”΄ Critical)

  • 100 untriaged issues β€” Backlog has grown significantly. All issues need triage to prioritize community reports. View untriaged issues

  • 52 unanswered questions (>7 days old) β€” Community members waiting for guidance. All questions are over 1 week old with no maintainer response. View questions

  • P0 Bug open since 2021 β€” #5805: MKLImports PDB not included with packages (@ericstj). This critical infrastructure issue has been open for 1743 days.

  • 16 blocking-clean-ci issues β€” CI/CD pipeline has known failures preventing clean builds. This blocks contributors and release readiness. View CI issues

    • #7419: TestAppendMany_SizeMoreThanMaxBufferCapacity triggers OOM killer
    • #7418: AutoMLExperiment_return_current_best_trial_when_ct_is_canceled
    • #7417: Code coverage build fails to instrument file in use
    • #7393: Resource contention in tests DownloadImageSet
    • #7343: SdcaLogisticRegression failing on Apple M1
  • 5 community PRs awaiting review β€” Including #6449 open for 1208 days (3.3 years). Community contributions are stagnating. View community PRs

  • 1 open security issue β€” #3604: Ensure documentation warns that models should be treated as code from security perspective. Open since 2019.

Timely (🟑 Warning)

  • 58 open bugs β€” No baseline for trend comparison (first run), but significant bug backlog exists.

  • Multiple stale PRs (>90 days) β€” 12 open PRs total, several very old:

    • #6449: Add DataViewSchema overloads (1208 days, community)
    • #6664: Generic DataFrame Math (1020 days)
    • #6749: Update Projects to .NET 8 (975 days)
    • #7094: Add Apache.Arrow Decimal128 support (714 days, community)

πŸ“¬ 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 @gmamaladze 2018-02-07 Never answered
#7174 Add AutoEncoder as Feature Selection Awaiting Input @superichmann 2024-06-15 2025-02-24
#6449 Add DataViewSchema overloads Community PR @FranklinWhale 2022-11-12 Never reviewed

Summary: 52 awaiting response Β· 100 untriaged Β· 5 unreviewed community PRs


πŸ”§ CI / Workflow Health

GitHub Actions (7-day summary)

Workflow Runs βœ… Pass ❌ Fail ⏹️ Cancel Rate
Locker - Lock stale issues and PRs 8 8 0 0 100%
Backport PR to branch 1 1 0 0 100%

Status: βœ… GitHub Actions are healthy (100% pass rate, 0 failures in last 24h)

Azure DevOps Status (Heuristic)

  • Open blocking-clean-ci issues: 16 πŸ”΄
  • Open Known Build Error issues: 16

Top blocking issues:

  • #7419: TestAppendMany_SizeMoreThanMaxBufferCapacity triggers OOM killer
  • #7418: AutoMLExperiment_return_current_best_trial_when_ct_is_canceled_with_trial_completed_Async fails
  • #7417: Code coverage build fails to instrument file in use
  • #7393: Resource contention in tests DownloadImageSet
  • #7343: SdcaLogisticRegression failing with LogLoss value above 0.5 on Apple M1

πŸ› Bug & Issue Landscape

Metric Current 7d Ago Ξ” Trend
Open issues (total) ~1000+ N/A β€” β€”
Open bugs 58 N/A β€” β€”
Untriaged issues 100 N/A β€” β€”
Open P0 1 N/A β€” β€”
Open P1 23 N/A β€” β€”
Issues opened (7d) 0 N/A β€” β€”
Issues closed (7d) 0 N/A β€” ⚠️

High-Priority Bugs (P0/P1)

# Title Priority Assignee Age (days) Milestone
#5805 MKLImports PDB not included with packages P0 β€” 1743 β€”
#7447 Legacy images need to be updated P1 β€” 314 β€”
#6588 Error: "Microsoft.ML currently supports 'x64' and 'x86'" for ARM P1 β€” 1098 β€”
#6370 Exposing the tree for multiclass classification P1 β€” 874 β€”
#6353 CreateEnumerable code fails in Visual Studio FSI P1 β€” 881 β€”
#5798 Add substitutes for IntelMKL methods for non x86/x64 builds P1 β€” 1751 β€”

πŸ”’ Security Issues

  • #3604: Ensure documentation warns that models should be treated as code from security perspective (open 2483 days) πŸ”΄

πŸ“₯ Pull Request Status

Metric Current 7d Ago Ξ” Trend
Open PRs 12 N/A β€” β€”
PRs merged (7d) 0 N/A β€” ⚠️
Community PRs awaiting review 5 N/A β€” β€”

Open PRs Needing Attention

# Title Author Age (days) Reviews Labels
#6449 Add DataViewSchema overloads to ConvertToOnnx @FranklinWhale 1208 0 community-contribution
#6664 (WIP) Generic DataFrame Math @JakeRadMSFT 1020 0 β€”
#6749 Update Projects to .NET 8 in MLNET 4.0 Branch @JakeRadMSFT 975 0 β€”
#7094 Add support for Apache.Arrow.Types.Decimal128Type @piyushdubey 714 0 community-contribution
#7406 [GenAI] Use BitsAndBytes for 4bit quantization @LittleLittleCloud 2 0 β€”

πŸ“Š 7-Day Trends

Metric Current Previous Ξ” Trend
Issues opened/day 0.0 N/A β€” β€”
Issues closed/day 0.0 N/A β€” ⚠️
PRs merged/day 0.0 N/A β€” ⚠️
GH Actions pass rate 100% N/A β€” βœ…

Note: This is the first run, so no trend data is available. Future runs will compare against this baseline.


πŸ’‘ Recommendations

  1. Urgent: Dedicate maintainer time to triage the 100 untriaged issues. Consider a triage sprint to categorize, label, and prioritize all pending community reports. This is blocking community engagement.

  2. Critical: Address the P0 bug #5805 (MKLImports PDB). This infrastructure issue has been open for 1743 days and affects debuggability across the ecosystem.

  3. Community engagement: Review and respond to the 5 stale community PRs. Especially #6449 (1208 days old). Either merge, request changes, or close with explanation. Stale PRs discourage future contributions.

  4. CI health: Create an action plan for the 16 blocking-clean-ci issues. Clean CI is essential for contributor confidence and release quality. Prioritize #7419 (OOM killer) and #7418 (AutoMLExperiment test).

  5. Answer unanswered questions: 52 questions are all over 7 days old. Even a brief "investigating" or "no plans" response is better than silence and shows the community is heard.

  6. Security documentation: Close #3604 by updating documentation to warn about treating models as code from a security perspective.


πŸ” Correlation Insights

  • Maintainer bandwidth crisis: 100 untriaged issues + 52 unanswered questions + 5 unreviewed community PRs suggests severe maintainer under-capacity relative to community engagement.

  • CI blocking community contributions: 16 blocking CI issues may be discouraging community PRs since tests are unreliable. Fixing CI could improve community contribution velocity.

  • Long-term technical debt: P0 bug open 1743 days + security issue open 2483 days + community PR open 1208 days indicates systematic backlog accumulation over years.

  • Zero velocity in last 7 days: 0 issues opened, 0 issues closed, 0 PRs merged suggests either (a) very low activity period, (b) work happening in other branches/repos, or (c) maintainers focused elsewhere. This is unusual for a .NET project of this size.

  • Good GitHub Actions health: Despite Azure DevOps CI issues, GitHub Actions are at 100% pass rate. Migration opportunity?


πŸ€– Generated by ML.NET Repo Health Check Β· 2026-03-04T18:29:57Z UTC

Generated by ML.NET Repository Health Check

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions