Skip to content

drill

The missing NOTICE

The upstream Apache library includes a NOTICE. The build ships the license but drops its applicable attribution notices.

Before inspecting the result

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

Prediction

Project boundary

2 components
bundleappLicenseRef-ProprietarylibraryApache-2.0
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.