How to add declared licenses for a package if the analyzer could not determine one #11725
-
|
Sometimes, packages do not set a declared license in their package metadata (e.g. package.json, pom.xml) even though they document a declared license somewhere else. In that case, the declared license is just missing from ORT's data. How can I set declared licenses for a package that misses it, e.g. with a package curation? The ORT documentation says:
But PackageCurationData.kt does not contain such a field. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
The original idea of declared licenses is that they are somewhat immutable, modulo mappings, but you cannot "invent" new declared licenses by declaring them yourself. Instead, the approach would be to conclude a license. Think of it as you coming to a conclusion what the declared license should be. However, be aware that a concluded license trumps all. So it overrides also any licenses detected by a scanner. This means you need to manually include any detected license into your concluded license, if it is different from the declared license. |
Beta Was this translation helpful? Give feedback.
The original idea of declared licenses is that they are somewhat immutable, modulo mappings, but you cannot "invent" new declared licenses by declaring them yourself. Instead, the approach would be to conclude a license. Think of it as you coming to a conclusion what the declared license should be.
However, be aware that a concluded license trumps all. So it overrides also any licenses detected by a scanner. This means you need to manually include any detected license into your concluded license, if it is different from the declared license.