Sebastian Schuberth

As a work-around, you could use `CONCLUDED_OR_DECLARED_AND_DETECTED` instead of `CONCLUDED_OR_DECLARED_OR_DETECTED` for now.

Hi @wujunhuge, thanks for the report. Unfortunately, most of the fields in the report were not fill out by you, making it hard for us to reproduce what the root...

> it looks like the ORT result JSON file has been tampered with. Or actually, judging from the file name name `bom.json` in your title, it looks like the input...

> Do I need to add any configurations when analyzing? That depends a bit on which, if any, package manager your C++ project is using. Can you share some details...

> Can my C++project be scanned without a package manager like Conan? It can be *scanned* in the meaning of running `ort scan` with the analyzer input, but none of...

And please note that [`ort analyze` currently expects the input directory to be under version control](https://github.com/oss-review-toolkit/ort/issues/2896). If that's not the case for you, you can trick ORT by creating a...

I believe all questions have been answered.

> There is no possible way to fix that, since they are not ours. For this, ORT has the concept of package [curations](https://oss-review-toolkit.org/ort/docs/configuration/package-curations). Community-maintained [curations are part of the `ort-config`...

> Maybe README may be extended with this information? The project's README is the wrong location for user-facing guides. Instead, please refer to the [docs on the website](https://oss-review-toolkit.org/ort/docs/getting-started/usage#curations-file).

> this page is not related to the GitHub Actions plugin, if I'm not mistaken. Well, those are the generic docs that apply to any way ORT is run. Also...