According to the topic below you don't create .NET specific packages since it is safe to override the warnings. However, without .NET specific packages you run into issues when you use Central Package Management (CPM) in Visual Studio with Transitive Pinning enabled in CPM.

When you use CPM without transitive pinning you can override the NU1701 on individual packages in the props-file, but when you enable transitive pinning to force vulnerable indirect dependencies to newer secure versions it becomes messy since the override solution doesn't work anymore. Having Essential Object binaries with target framework set to .NET and not .NET Framework would be really helpful to avoid awkward and potentially insecure workarounds like disabling NU1701 completely. Or do you have another solution to this problem?

Your original statement about not needing a .NET specific package.
https://www.essentialobjects.com/forum/postst12416_EOPdf-Nuget-Package-on-NET-Core-6-shows-exclamation-warning-icon.aspx