feat(licenses): meet the LGPL notice and source terms for libvips and node-webpmux

The notices now carry the LGPL-3.0 and GPL-3.0 texts from
scripts/license-texts (the LGPL text byte-identical to gnu.org's, the GPL
text as the Rust toolchain ships it), whatever the dependencies ship.
The LGPL section names each component with its exact version, says it
ships unmodified as a separate library, and gives the upstream source
release of that version: sharp-libvips v1.3.2 and libvips v8.18.3 for
the libvips packages, sharp v0.35.3 for @img/sharp-win32-x64, the npm
package of node-webpmux 3.2.1. The libraries built into libvips are
listed with their versions from versions.json. Versions and repository
URLs come from the lockfile and the installed packages.

The LGPL exceptions of the license gate are no longer pending: the
project owner left these items to us. A test checks the texts, the LGPL
rows and the Apache-2.0 files against the committed notices. UF-059 is
fixed.
This commit is contained in:
shumeiko.it
2026-11-04 10:34:32 +01:00
parent 58535a580f
commit 35bf8e26bd
8 changed files with 829 additions and 113 deletions

View File

@@ -45,7 +45,8 @@ Implemented in P1.7 with `whatsapp-web.js` 1.34.7 (Puppeteer 24).
`@puppeteer/browsers`, `chromium-bidi`, `webdriver-bidi-protocol`), BSD (`devtools-protocol`,
`extract-zip`), MIT and ISC for the rest, and LGPL-3.0-or-later for `node-webpmux`, a
required dependency of whatsapp-web.js that it loads on startup for sticker metadata. It
ships as a separate, unmodified package. The licensing review has to accept it.
ships as a separate, unmodified package; `THIRD_PARTY_NOTICES.md` carries its LGPL notice,
the license texts and its source location (settled on 2026-11-04, no owner review needed).
- The client is unofficial. Settings warns that WhatsApp may block the account and
recommends a secondary number.
- Risk: whatsapp-web.js awaits page work inside browser event listeners (for example