Hi there - Thank you for sharing your impressions on your use of our tool!
I wanted to provide some insight regarding the inclusion of packages not directly declared in your BOM. By default SOOS inspects not only your direct dependencies, but also your transitive dependencies to ensure that we find any issues, including those lurking deep in your dependency tree. This can be a shock if you've been using other tools that only look at your direct dependencies. You can see this within the dependency tab of your project details along with the introduction paths that will tell you exactly where that dependency came from.
That said, this dependency tree scan depth setting is customizable either globally or at the project level so you can configure your scans to only inspect direct dependencies if you would prefer that. Additionally, you can choose to include or ignore dev/test dependencies, and/or use lock files as the source for the dependency tree.
We're confident in our abilities to locate issues and resolve dependencies, but if you think you found a problem, definitely let the support team know and we'll take a look. We are also more than happy to provide you guidance and resources so you can fine-tune your scans in a way that better fits your needs.
You can get in touch with SOOS Support using the 'Help' link in the left nav. menu within the app or using the support widget found on our main site.
As for CSV exports, these are on our list to be added soon! In the meantime we have many other export options, including SARIF, SPDX SBOMs, VEX, and CycloneDX SBOMs in a variety of file types (JSON, HTML, Text, HTML).