- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper audits whether permissively licensed agent components retain their license text and required copyright notices across publication, reuse, composition, and distribution. It studies Skills, MCP servers, and Plugins using ScanCode-based payload detection, content matching, provenance and timing filters, and installation and registry-archive checks. The authors assess 345,371 Skill occurrences and report that 59.4% lack a complete payload along their governing directory chains. Among time-eligible copies with complete references, they report payload loss in 41.1% of Skill file copies and 58.5% of MCP server file copies. Controlled installations with Claude Code and Codex and inspection of 121 registry archives examine whether repository-level notices survive delivery. The central finding is that complete repository documentation does not ensure complete component copies: preservation depends on whether the copied or delivered unit encloses the relevant notices. The authors also describe a replication package of data, code, and audit artifacts.
Critical strengths
S1: The paper moves beyond checking repository license labels to tracing the material retained in component copies, bundled Plugins, installed directories, and registry archives. The distinction between a complete repository and a complete delivered component is relevant to publishers and distribution tooling, and the installation and archive checks make the contribution more concrete than a metadata-only audit.
S2: The authors exclude copies predating their reference's complete payload, examine README notices and repository weighting, disclose concentration in large collections, and compare two installers. The byte-preservation checks also help locate the measured loss at directory selection. These controls address important alternative explanations and deserve credit.
Critical weaknesses
W1: The C4 delivery boundary does not yet establish the stronger recipient-level interpretation. Section 3 compares the full repository, the selected directory, and the installed cache (pp. 5, 7–8). This establishes whether the selected plugin copy is self-contained, but Section 2.2 also recognizes that accompanying documentation can carry notices. Current Claude Code loading documentation distinguishes fetched marketplace copies from plugin-cache copies, suggesting a concrete alternative: an ancestor license could reach the recipient through an automatically fetched marketplace checkout while remaining absent from the plugin cache. This must be checked for the paper's pinned versions and source types, current documentation alone does not invalidate its historical results. Please distinguish pre-seeded source snapshots from automatically delivered artifacts and show whether required notices are absent from the complete acquisition flow. Otherwise, the result should be framed as a lack of self-contained notices in the selected copy, with a separate explanation of its implications for recipients and subsequent redistribution. This affects the interpretation of a central contribution beyond existing repository-level audits.
W2: The provenance-to-required-notice mapping needs more direct validation. Section 3 uses the earliest dated matching Skill body as a reference and tests preservation of its required holders (p. 4). Temporal precedence and content equality do not by themselves establish the relevant origin or distinguish a shared upstream source. Likewise, notices found in ancestor directories need to be connected to the particular copied component. The timing gate addresses postdated payloads, and the reported 83.4% MCP pair precision validates candidate matching, but neither alone validates the final attribution-loss labels. This matters because every failed C2 Skill copy is missing a required holder, and 79 of the 89 failed C3 Skill copies retain matching license text (pp. 6–7). Please provide the component-to-notice applicability rules and existing or bounded manual validation of the final labels, including sensitivity to uncertain provenance or unrelated notices. This concern does not negate C1's widespread missing license text; it affects the stronger attribution-tracing conclusions. Relevant validation may be in the appendices unavailable to this assessment.
Questions for authors
Q1: For the pinned Claude Code/Codex versions, what exact files are automatically acquired during marketplace registration and plugin installation, beyond the final plugin cache? Do representative failed C4 cases retain the required notices in an automatically fetched marketplace copy or accompanying documentation? Please separate these from manually pre-seeded repositories and report cache-level versus complete-acquisition outcomes, or identify the existing supplementary evidence that establishes this distinction.
Q2: How are notices in a reference's governing chain determined to apply to the matched component, and how are common upstream sources, unrelated notices, and ambiguous holder matches handled? Please identify any existing manual audit of the final C2/C3 attribution-loss labels and its results, or provide a bounded stratified check and show how excluding uncertain cases changes the reported outcomes. Candidate-pair precision should be distinguished from the precision of the final loss labels.