Sebastian Schuberth

> Hm, I still believe how ORT server's UI groups things is out-of-scope of the ORT project. What about > For example, `ort report --help` could list the type of...

> Not liking INTERNAL_USE enum Then please make constructive proposals for other names.

I'm cancelling this idea for now, mostly due to: > The problem with this are custom plugins and template reports where the type cannot be known ahead of time.

@fviernau mind having a look as I have some follow-up changes?

I just discovered https://lfx.rushstack.io/, BTW, which looks like a useful tool to analyze / debug PNPM lockfile issues.

> Duplicate of #1716 Indeed, please close this issue @AlejandroYuste.

If mappings would be configurable, they should probably also be implemented as plugins, which in turn relates to https://github.com/oss-review-toolkit/ort/issues/10214.

Thanks for the clarification. It'd indeed be good if that explanation was in the docs as well!

FYI, [this](https://github.com/gradle/github-dependency-extractor/issues/20#issuecomment-1524817722) seems to be how the GitHub dependency submission API seems to deal with the issue (i.e. allow incremental uploads than amend existing ones).

In today's ORT community meeting it was proposed to close this in favor of https://github.com/oss-review-toolkit/ort/issues/10156 and essentials requiring users to always run the ORT analyzer in the environment they create...