Binaries contained in nuget are not generated using a strong name

[alonsoto]

Binaries contained in your NuGet are not generated using a strong name, when we use your asset as third party we receive the advise from Cybersecure auditory.

Use strong-naming have some benefits explained by Microsoft official documentation

https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming

The benefits of strong naming on .NET Framework are:

• The assembly can be referenced and used by other strong-named assemblies.
• The assembly can be stored in the Global Assembly Cache (GAC).
• The assembly can be loaded side by side with other versions of the assembly. Side-by-side assembly loading is commonly required by applications with plug-in architectures.

Thanks in advance.

[ssg]

You should strong name your open-source .NET libraries if their targets include .NET Framework or .NET Standard. Strong naming is not required for libraries that target .NET Core/5+ only.

https://github.com/dotnet/docs/blob/main/docs/standard/library-guidance/strong-naming.md#create-strong-named-net-libraries