The Manifest/ Practice Practice SBOMs and open-source licences: how to avoid trouble By SBOMBox SBOM experts · 12 September 2026 · 2 min read Short answer: every open-source component comes with a licence, and the SBOM lets you check them all.
Three broad groups Permissive (MIT, Apache 2.0, BSD): few conditions, mostly credit. Weak copyleft (LGPL, MPL): changes to the component itself must be shared. Strong copyleft (GPL, AGPL): may require you to share your own code, depending on how you use it. Decide which licences you allow, and check new components automatically against that list. Ask a lawyer about unusual cases.
This is general information, not legal advice. Confirm how the rules apply to you with counsel.
In this guide Vulnerability and supplier management CVSS, EPSS, KEV: which vulnerabilities should I fix first? What is CISA KEV? The Known Exploited Vulnerabilities catalogue, explained What is EPSS? The Exploit Prediction Scoring System, explained What is VEX? How to say 'this vulnerability does not affect us' CSAF, VEX and security advisories: what should you publish? How to get SBOMs from your suppliers (and check they are any good) How to answer a customer's SBOM and security questionnaire SBOMs and open-source licences: how to avoid trouble All guides and resources Check your own SBOM in under a minute. Drop a CycloneDX or SPDX file on the free checker and get a quality score across 8 categories. No account, nothing stored.