In VersionEye it’s very easy to setup a license whitelist. A license whitelist describes licenses which are allowed in your organisation. You can even have multiple license whitelists per organisation. That way different projects can have different license whitelists. That makes totally sense because licenses have different obligations. Some licenses can be used in a cloud environment but not for mobile apps.
However, most people don’t know much about software licenses. They simply don’t know what to put on a license whitelist and what not. That’s why VersionEye has a default license whitelist now. It contains a small set of software licenses which can be used in any environment. The default license whitelist currently contains this licenses:
- Apache-1.0
- Apache-1.1
- Apache-2.0
- BSD
- BSD-2-Clause
- BSD-3-Clause
- BSD-4-Clause
- BSD-4-Clause-UC
- CC0
- CC0-1.0
- ISC
- MIT
- Public Domain
- WTFPL
This license whitelist has always the name “default_lwl” and for newly created organisations it’s marked as default license whitelist. That means it gets assigned to all new created projects and all the project dependencies are compared against that whitelist.
Of course you can edit the “default_lwl” any time. You can remove licenses from it and you can add new licenses to it any time. It’s just a suggestion to start with.
Let us know how this works out for you.
Open Source License Compliance & Security 