What is the state of Microsoft.Management.Infrastructure? #24794

We’re trying to make sense of how WMI/CIM is intended to be consumed from .NET:

• .NET says System.Management is intended to support porting from .NET Framework, and shouldn’t be used by new code.
• But, the MMI repo is archived as of Jun 15, 2024, and was last pushed to on Aug 6, 2019, just before the 2.0.0-preview.1 release.
• The NuGet package was last pushed to on Nov 3, 2023, while System.Management is much more frequent since it is tied to .NET release cycles.
• SM currently has 76.3K average daily downloads, while MMI has 5.3K. Yet, SM has limitations such as lack of nullable types, lack of support for IPv6 on ManagementObjects (ManagementObject set IPv6? dotnet/runtime#94552), and most importantly, dependence on .NET Framework 4.6.2+.

This has been asked several times over the past 2 years (#20441, PowerShell/MMI#55, PowerShell/MMI#56, dotnet/runtime#110573) with no answer.

So - could we get an understanding of where MMI stands?

• Is MMI still maintained?
• Is it intended to be consumed by third-parties, or only by PowerShell? The Windows runtime package is strangely licensed (Confusing licensing in Microsoft.Management.Infrastructure 3.0.0 nugets #20798).
• Why is the source code several versions behind, and now archived?
• Where should bug reports/feature requests be sent?