Every open-source artifact in your project—whether it’s a package, gem, wheel, dependency, or similar—may either lack a license entirely or come with one or more licenses detailing the terms and conditions for its use. These licenses are set by the project maintainer(s), not ActiveState.
You can find out about the types of software licenses using external resources, including
We recommend you consult with your own legal council, compliance team, or open source team to learn about software licenses and what policies you may have.
You can generate an SBOM to find the license information appropriate to your project. The resulting SBOM is our best effort to list all applicable licenses relating to your project, but due to the iterative nature of software, it is not guaranteed to be an exhaustive list.
There are multiple kinds of licenses in the ActiveState SBOMs
Use additional methods of verification, including searching for maintainer-declared licenses.
A common way to find the maintainer-declared license is to look directly in the package and/or source repository. Examples are included below.
This example brings you to a GitHub project, and the maintainer license is on the right-hand information panel.
This example brings you to a GitHub project, and the maintainer license is on the right-hand information panel.
Another method of finding the license(s) is to review the source code itself. To ensure you are getting the exact version of code built by ActiveState, you can pull down our copy of the source code by using our API and locate license information.
To find/search for additional license files by following our guide to download your project ingredients.