Replies: 3 comments 1 reply
-
Beta Was this translation helpful? Give feedback.
-
|
What a coincidence :) On the discussion you linked:
One can achieve this ? |
Beta Was this translation helpful? Give feedback.
-
So Bazel uses Conan. Couldn't we just add an option to |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, the declared license of a package cannot be curated. I assume this is a decision made in the past because it's pretty dangerous and there was no requirement to support it.
We have however a use case for such curation.
A project of our organization is using Bazel and Conan. The same packages are present in both package managers because the former uses the latter.
The owner of this repository requested that we consider Bazel as the single source of truth and that we don't process Conan packages.
The issue is that the Conan packages have more metadata than their equivalent in Bazel. This is because Bazel doesn't have any property for:
declared licenseauthors(it hasmaintainerswhich is something else).Additionally, some Advisors such as VulnerableCode don't report vulnerabilities for Bazel packages, but Conan packages are usually supported. Therefore, curating the
pURLof a package could be interesting to fetch those vulnerabilities.The current curation system in ORT allows to curate the
authorsand thepurlof a package. However thedeclared licensecannot be curated.Would it be possible to modify
PackageCurationDatato add the declared license ? If this deemed dangerous, maybe with an unsafe configuration flag ?If this requested change is not possible, which alternative could fulfill our requirement ? Package configurations don't seem like a good match, because with still want the unaltered results of the scanner.
Beta Was this translation helpful? Give feedback.
All reactions