Open andreycha opened 1 week ago
Okay, the nasty whitespace comes from nuspec file: https://api.nuget.org/v3-flatcontainer/Mvc4Futures/4.0.20710/Mvc4Futures.nuspec
Would it be possible/make sense to trim all urls for example?
I think a valid URL can never start or end with a whitespace, so I see no problem with that
True. DependencyTrack has recently started to validate BOMs according to the specification. It requires all URLs to be valid RFC 3987 IRI-references where whitespace is not a valid character.
Hi,
Version
3.0.5
(tried also3.0.8
) seems to generate invalid license URL for one of the components. Note whitespace at the end:BOM is generated as following:
Not sure where the whitespace comes from, component page on Nuget.org has a valid URL.
Would appreciate any help.