drill
Covered files in a larger work
An MPL library ships inside a proprietary application. Identify a source location for the covered library file; the application remains a separate non-MPL source file.
Before inspecting the result
What does this supplied release need before its modeled requirements are met?
Project boundary
2 components| From → to | Connection | Semantics |
|---|---|---|
| app → library | bundle | intimate |
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
Expression builder
| Alternative | Required licenses |
|---|---|
| 1 | MIT AND LGPL-3.0-only |
| 2 | Apache-2.0 AND LGPL-3.0-only |