license-compliance
Safeguard articles tagged "license-compliance" — guides, analysis, and best practices for software supply chain and application security.
91 articles
What a WhiteSource Scan Actually Checks (and How Mend Changed It)
A WhiteSource scan is a software composition analysis run that inventories your open source dependencies and flags known vulnerabilities and license risks. Here is what it looks at and how the Mend rebrand affects your pipeline.
Types of Open Source Licenses
A breakdown of permissive, copyleft, and source-available license types—MIT, GPL, AGPL, SSPL—and why misclassified licenses create hidden supply chain risk.
Copyleft vs Permissive Licenses
Copyleft and permissive licenses trigger different legal obligations. Here's how GPL, AGPL, MIT, and Apache 2.0 actually differ — with real lawsuits and relicensing cases.
Open Source Security Platforms: What They Actually Do
An open source security platform isn't one tool — it's usually a combination of SCA, license scanning, and vulnerability intelligence stitched into a pipeline that watches your dependencies.
What Are the Different Types of Licenses in Software? A Security View
The different types of licenses in software fall into a few families - permissive, copyleft, weak copyleft, and proprietary - and each carries distinct legal and supply chain obligations.
Copyleft Licenses: What They Mean for Your Code
A copyleft license requires that derivative works stay under the same license, which can force you to open-source code you thought was proprietary. Here is how copyleft works and how to manage the risk.
The MIT License, Summarized: What It Permits and Requires
A plain-English MIT license summary: the one condition it imposes, the freedoms it grants, and the compliance step teams still manage to miss.
OSS License Types Explained and Their Compliance Risks
A field guide to OSS license types, from permissive MIT and Apache to copyleft GPL and AGPL, and the obligations each one puts on the code you ship.
The GPL License Explained: What It Means for Software Security
A practitioner's walkthrough of what the GPL license actually requires, why it matters for your dependency tree, and how it intersects with software security and compliance.
Open Source License Comparison: MIT, Apache, GPL, BSD
MIT, Apache 2.0, GPL, and BSD dominate the open source ecosystem but differ sharply on patent grants and copyleft obligations — here's a side-by-side comparison.
The BSD License: Full Form and Terms Explained
The BSD license full form is the Berkeley Software Distribution license — a permissive open-source license with fewer obligations than the GPL family, and a few variants worth telling apart.
GNU AGPL vs GPL: When AGPL Actually Applies
The GNU Affero General Public License v3.0 closes the network-use loophole that GPL leaves open — here's exactly when that difference matters for your codebase.
Self-healing security runs on Safeguard.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.