Given I have a component that is associated with a license TrustSource does not know. What can I do?
TrustSource maintains a repository with common licenses. These licenses have been analyzed and grants as well as obligations have been isolated. Licenses are categorized and managed carefully. As this process is not always just straightforward, we decided not make the editing of the repository public.
However, this work is very useful and every license adds to the knowledgebase of all users. All users profit form a single entry. This makes it so useful in sharing the knowledge and the experience form different organizations.
So we decided to provide this as part of our service. Please send the link of the origin of the missing license or the containing repository to firstname.lastname@example.org. Our team will assess the license and file it to the repository for the benefit of the community.
If you want to add a private license, that you do not want to share with others, e.g. YOUR-COMPANY-LIC, see "How to add private licenses".
If you just want a name to be associated with a praticular license type, e.g. "apache" shall always match to APACHE-2.0, see "How to create a new alias for a license".