Skip to main content

Licenses

License encyclopedia

What each common third-party license actually grants, what it does not, and where teams get it wrong. Plain language. Not legal advice.

Last updated: August 31, 2026

121 of 121

Permissive licenses

When you ship permissively licensed code, keep the required copyright notices and license text with every copy. Your own source can usually remain private.

Weak copyleft

When you ship a changed weak-copyleft library, provide that library's source under the same license and preserve its notices. Your surrounding application can usually remain closed.

Strong copyleft

When you ship a combined program with strong copyleft code, recipients can require the corresponding source of the whole program under the same license.

Network copyleft

Running network-copyleft software as a website or API can trigger a source duty even when no file is handed over. Check the deployed service as well as shipped artifacts.

Public domain and no-condition grants

These grants usually impose no notice, attribution, or source duty. Record them anyway so the published inventory remains complete.

Source available

Source-available terms limit use even though the code is readable. Match production, commercial, and competitive use against the actual license text before release.

Proprietary and commercial

Compliance depends on the agreement your company signed, not a public license summary. Verify the order form, permitted use, term, and redistribution rights.

Special cases

No license, multiple choices, exceptions, and custom identifiers cannot be cleared from the short id alone. Record the governing text and review that exact case.

These guides are educational. They are not legal advice, and they do not certify a product.

Cookies on sourcetrust.dev

We use essential cookies for security, including abuse prevention on our site scan and walkthrough request form. With your permission, we also use optional analytics and diagnostics (Google Tag Manager on this site, and the Sentry browser SDK on the SourceTrust application when configured). See our cookie policy.