drills
Repair the release
Sixteen supplied projects. Meet the actual license, boundary, attribution and evidence requirements.
01 · Foundations
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.
not started
02 · Foundations
The permissive release
A build removed the library copyright attribution. Repair the shipped notices without changing the library's license.
not started
03 · Copyleft
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.
not started
04 · Copyleft
One option or both?
The library offers LGPL-3.0-only OR MIT. Record one complete offered alternative, then meet its obligations.
not started
05 · Linkage and boundaries
A replaceable library
The LGPL library is dynamically linked. Its source location is included, but the application has no documented compatible replacement mechanism or debugging permission.
not started
06 · Linkage and boundaries
Refactor the integration
A GPL utility is currently bundled into a proprietary application. You may replace the integration with an independent subprocess using plain input/output, or a separate REST service. Preserve the utility and its source offer.
not started
07 · Network use
The modified service
The modified AGPL library and app are one service exposed to remote users. The app owner authorizes an AGPL release. Meet the combined-work terms and source-offer obligations.
not started
08 · Network use
Remote users inside the company
The app is MIT and uses a modified AGPL library. Employees interact with this combined program over a network. There is no external distribution. Supply the modeled source offer to those interacting users.
not started
09 · Attribution
The missing NOTICE
The upstream Apache library includes a NOTICE. The build ships the license but drops its applicable attribution notices.
not started
10 · Attribution
A file without its history
Repair the REUSE declaration on src/library.ts. Preserve the actual holder and SPDX MIT identifier; the required license text is already present.
not started
11 · Governance
Signed off by whom?
The patch author is Alex Example <[email protected]>. A DCO is a certification, not copyright assignment. Include the author's sign-off in COMMIT.txt and a declaration that the contribution stays under MIT.
not started
12 · Governance
The version's change date
This BUSL version converts to MIT on 2026-10-01. Evaluate the supplied date and add the license and attribution required by the effective grant. Keep the original BUSL evidence.
not started
13 · Supply chain
The nested choice
The distributed app is GPL-2.0-only. A transitive library offers Apache-2.0 OR MIT. Select a compatible branch without changing third-party grants.
not started
14 · Supply chain
An SBOM with a ghost dependency
Repair bom.json so it describes the supplied project and has complete, unique references. The SBOM generator is available, but validate the result.
not started
15 · AI artifacts
Code and weights have different grants
The MIT application distributes Llama 3.1 weights. The supplied use is acceptable and the licensee had 10,000 monthly active users at release. Complete the model attribution surface.
not started
16 · AI artifacts
The generated snippet
A coding agent copied a snippet from a known MIT source. Preserve its provenance and the permission supplied by its owner. AI generation is not evidence of permission.
not started