Open Source License Compatibility Checker
Check the licenses in your SBOM against how you ship, and see which ones need attention.
From an SBOM
Pull every component's license from a CycloneDX or SPDX file.
Or add licenses
Type an SPDX identifier or expression, such as MIT or GPL-2.0-or-later OR MIT.
Try , , , .
How do you ship the product?
License obligations depend on whether, and how, the software reaches other people.
How it works
- Add your licensesLoad a CycloneDX or SPDX SBOM to pull every component's license, or type SPDX identifiers by hand. Nothing is uploaded.
- Say how you shipInternal use, a hosted service, a closed-source binary or an open source project. Obligations depend on it.
- Act on the resultResolve conflicts, review the rest, and follow the obligations list. Export the result as CSV for legal review.
Enforce your license policy on every build.
SBOMBox policies allow or deny licenses per project, fail the CI check when a denied license appears, and keep the record for audits and customer questionnaires.
Frequently asked questions
Which licenses cause problems in commercial products?
Strong copyleft (GPL) when you distribute binaries, network copyleft (AGPL, SSPL) when you offer a service, and source-available licenses (BUSL, Elastic, Commons Clause) that restrict commercial or competing use.
What about dual-licensed packages like MIT OR GPL-3.0?
With OR you may pick either license, so the tool uses the least restrictive option. With AND you must meet both, so the most restrictive one applies.
Is the result legal advice?
No. It is a fast triage based on common interpretations of each license family. Have counsel review anything flagged before you ship.
Can I enforce a license policy automatically?
Yes. SBOMBox policies allow or deny licenses per project and fail the build or the release check when a denied license appears.