You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Contents:

 

Licenses Policies Management

 

As explained in Insights Licenses#LicenseRisk there's a default policy to assign a License Risk to licences found during Insights analysis.
The default License Risk Policy works as follows :
  • High is associated to Copyleft, Copyrighted and Propietary
  • None is associated to PublicDomain, Permissive and WeakCopyleft
  • Unknown is associated to licenses that without a License Type.

 

This default policy is quite conservative, it raises an alert when some license might have a legal implication. But, depending on the concrete case, the alert might not apply to your organization or you don't need to be alerted about certain licenses. 

In these cases, Kiuwan Insights' Licenses Policies lets you to change the License Risk of any License to suite your concrete needs.

 

Licenses Policies Management


Custom changes to the level of License Risk of a License can be applied to several scopes

 

Changes to the level of Risk of a License

Scope

Precedence

Meaning

Global

1

Change to the license are global, i.e. it applies to all components of all the apps that are using that license.

Change applies to current components as well as new components discovered in future analyses.

Application

2

Change to the license applies to all components of selected app that are using that license.

Change applies to current components as well as new components discovered in future analyses.

Components belonging to other app using this license remain unchanged

Component

3

Change to the license applies to the selected component, regardless the app using the component

App-Comp

4

Change to the license applies to the selected component in the selected app.

Selected components using this license belonging to other app remain unchanged.

 

Precedence column means the apllicability in case of conflicts, being applied the case with higher precedence value.

For example, we could have configured:

  • License L is High for application A (application scope: 2)
  • License L is Medium for component C (component scope: 3)

What will be the level for component C in application A ? Precedence 3>2, L will be Medium for C in A.

 

Changes are retroactive

Changes to Licenses are applied retroactively, i.e. changes will be applied not only to future analyses but also to past analyses

 

 

 

 

 

  • No labels