Plugin ZIPs omit license texts for bundled third-party components #345
Labels
No Label
area:auth
area:docs
area:export
area:ops
area:storage
area:supply-chain
auth
backend
blocked
collab
deployment
docs
effort:L
effort:M
effort:S
frontend
plugins
qa
vs-nfd
vs-nfd:blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: stwaidele/dorfteich#345
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The installable plugin ZIPs redistribute third-party material without the license texts their licenses require:
src/main/webappand drops the tarball's rootLICENSE.plugin.js(both MIT) and ships Excalidraw's fonts (SIL OFL 1.1 / MIT). MIT requires the copyright and permission notice with copies; OFL requires the license to accompany the fonts. The npm package ships no license files at all.plugin.js(MIT et al.), same gap.Fix: every plugin ZIP that redistributes third-party material gets a
licenses/directory:licenses/THIRD-PARTY-NOTICES.txtgenerated mechanically from the esbuild metafile (every node_modules package that actually ends up in the bundle, with its license expression and shipped license file), so the list can never drift from the bundle.LICENSEextracted from the pinned tarball; excalidraw adds committed license texts for Excalidraw (MIT) and the bundled fonts (OFL-1.1 full text + per-font attribution), since upstream ships none.Found during the pre-publication license audit (2026-08-16). The api-side package validator accepts additional ZIP entries, so no server change is needed.