Skip to content

Lesson 1 · foundations

The default state

Copyright exists before a repository has a LICENSE file.

Copyright generally arises when original expression is fixed. A public repository makes source visible; it does not by itself grant permission to modify or redistribute that source. Platform permissions and an open-source grant are different instruments.

Identify the version, the holder and the grant before deciding what you can ship. A package manifest with no license field is missing evidence. It is not evidence of the MIT license, and a parent package cannot grant rights to every dependency.

In this project, the holder supplied a version-specific permission file. Record that actual grant and preserve its terms and attribution. If the owner had supplied no permission, the appropriate result would remain unresolved rather than a guessed green check.

Try it: Public does not mean licensed

The owner has supplied a signed MIT grant in permissions/library.txt. Record the evidenced license and preserve the grant.

Before inspecting the result

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

Prediction

Project boundary

2 components
bundleappLicenseRef-ProprietarylibraryNo license
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.