Skip to content

Lesson 2 · foundations

The permissive trinity

Permission to distribute carries conditions.

MIT, BSD 2-Clause and BSD 3-Clause permit broad reuse, including commercial reuse. Their conditions still travel with copies. Preserving copyright and the relevant license text in a readable accompanying artifact is an ordinary way to meet redistribution requirements.

BSD 3-Clause adds a non-endorsement condition. The historical BSD 4-Clause also has an advertising acknowledgment, which can create compatibility problems. The number of clauses is substantive, not a cosmetic naming convention.

Apache 2.0 adds an explicit patent grant, patent termination conditions and change notices. If an upstream NOTICE is supplied, retain its applicable attribution notices. Apache does not require you to invent an upstream NOTICE that never existed.

Minification can discard comments. Inspect what the release actually ships: the bundle, accompanying licenses, documentation and notice surfaces. A missing inline banner does not alone establish a violation if compliant notice artifacts accompany the release.

Try it: The permissive release

A build removed the library copyright attribution. Repair the shipped notices without changing the library's license.

Before inspecting the result

What does this supplied release need before its modeled requirements are met?

Prediction

Project boundary

2 components
bundleappLicenseRef-ProprietarylibraryMIT
Dependency relationships
From → toConnectionSemantics
app → librarybundleintimate

Supplied facts

Distribution
binary
Network interaction
No
Intended use
internal
Evaluation date
2026-10-24
Policy
learning

These facts define the simulation. Evidence declarations stand in for actual corresponding source, relinkable objects and release materials.

Components

Declared license
LicenseRef-Proprietary
Modified files
None
Artifact
code

Third-party grants remain fixed unless this scenario supplies authority to change them.

Project artifacts

Evidence artifact format

Source offers contain “component: id” and “source: https://…” on separate lines. Covered-file offers also list the covered paths. Relinking declarations contain “replace-compatible-library” for dynamic linking or “relink-object-files” for static linking, and “reverse-engineering-permitted”. These declarations model supplied release artifacts.

License reference

permissions
commercial-use, modifications, distribution, private-use
conditions
include-copyright, include-license
limitations
liability, warranty
Read authoritative terms ↗

Expression builder

Each row is one selectable alternative. AND retains every term in a row.
AlternativeRequired licenses
1MIT AND LGPL-3.0-only
2Apache-2.0 AND LGPL-3.0-only
Results appear after submission.