Sebastian Schuberth

> I also attempted using the `nuget-inspector` directly and produced the following result: [nuget-inspector-result.json](https://github.com/user-attachments/files/20548343/nuget-inspector-result.json). From my understanding, it does not provide any information on the graph structure of the dependencies....

Could you maybe try https://github.com/microsoft/component-detection on your project to see whether you're getting expected results with it? If so, we might consider switching to it from `nuget-inspector`.

> Have you given further thought to the possibility of switching to [component-detection](https://github.com/microsoft/component-detection)? I still believe the idea is good, but I have no idea yet whether it's feasible, esp....

> I have tried to draw up a comparison between the data contained in the analysis results Thanks a lot for the effort! That's really useful. I was also looking...

> Fixes #9298 Nit: Missing period at the end of the sentence.

@wkl3nk could you try if https://github.com/oss-review-toolkit/ort/pull/9304 instead would also fix your issue?

Yes, that's exactly what my PR is about. But could be that there's still something wrong in my implementation.

> I don't know if this is valid, or if it is better to say something like "There are no namespaces in Go". You may want to refer to [this...

I still believe we should solve this differently, in a more generic way. While Go apparently does not have namespaces, the purl standard treats them as if Go had namespaces....

In any case, @wkl3nk as mentioned [here](https://github.com/oss-review-toolkit/ort/issues/9298#issuecomment-2419213085) please add a test for this (in a new commit that could easily be cherry-picked) so we can verify the fix also for...