My first suggestion: I would link the limitations section to the privacy section, as currently it may pick up private library names and publish them.
I would also add to privacy the scope of the scan, e.g. that it will only look with in the given directory, and that this needs to be specified so that it won't accidentally scan the current working dir.
Lastly, at least while in Alpha, I would love to have a dry-run mode, ideally on by default, which allows me to bypass sending any information while ideally review the report it generated. This would help me to build some trust first, independently of whether the information is public to begin with.
My first suggestion: I would link the
limitations
section to theprivacy
section, as currently it may pick up private library names and publish them.I would also add to
privacy
the scope of the scan, e.g. that it will only look with in the given directory, and that this needs to be specified so that it won't accidentally scan the current working dir.Lastly, at least while in Alpha, I would love to have a dry-run mode, ideally on by default, which allows me to bypass sending any information while ideally review the report it generated. This would help me to build some trust first, independently of whether the information is public to begin with.