-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft.Web.LibraryManager.Build starting to show security warnings #770
Comments
I'm not reproducing this with a new web project:
and both libman packages (.Build and .Cli) should not bring transitive references to that package. Can you include the output of |
I confirm that it won't reproduce on typical web project, but it will reproduce on Blazor if you are using There is minimal reproduction https://github.com/leotsarev/ReproduceLibManTest |
I too am seeing these warnings after upgrading one of my Blazor WebAssembly projects to .NET 9. Is there a way to suppress this warning ? |
|
Describe the bug
Microsoft.Web.LibraryManager.Build starting to show security warnings
To Reproduce
<PackageReference Include="Microsoft.Web.LibraryManager.Build" Version="2.1.175" PrivateAssets="All" />
into the projectExpected behavior
No security warnings
Additional context
NOTE: This is not a actual vulnerability
This is known problem in Nuget when using netstandart2 projects. dotnet/sdk#42651
It could be worked around by moving to CPM and pin System.Private.Uri version, but users are discouraged to reference System.Private.Uri directly, and it's frustrating for users to get this warning from official Microsoft package
It's recommended than:
Microsoft.Web.LibraryManager.Cli
provided that target modern .net (net9 or net8)Microsoft.Web.LibraryManager.Cli
to a non-vulnerable versionThe text was updated successfully, but these errors were encountered: