ekklesiaandClaude Opus 5.5
afaf3a853c
CI / verify (pull_request) Successful in 1m4s
CI / infrastructure-smoke (pull_request) Successful in 36s
CI / migration-smoke (pull_request) Successful in 1m53s
CI / package-release (pull_request) Successful in 34s
CI / image-build (pull_request) Successful in 30s
CI / deploy-smoke (same-origin) (pull_request) Successful in 47s
CI / deploy-smoke (split) (pull_request) Successful in 1m28s
CI / package-publication (pull_request) Successful in 50s
sharp 0.35.4 carries a production-relevant librsvg advisory (GHSA-wq5f-xc86-pv6w). Its fix, sharp
0.35.5, loads @img/sharp-libvips-linux-x64 1.3.4, which ships no licence material either. This adds
the reviewed supplement for that exact package (ADR 0052) and moves the packager's native proof to
sharp 0.35.5, so a later 0.2.1 release can package it on linux-x64-glibc. Nothing in module-pack's
code changes: supplement selection is already by exact name, version, and content digest.
- Supplement: license-supplements/@img/sharp-libvips-linux-x64/1.3.4/
- content digest ekklesia-content-v1:sha256:2927fe11493461fa34847191d0b9b1c6441007c3e99f306e5708cb07fb0a5e59;
- 190 components and 146 hashed texts;
- assembled with the same method as 1.3.3's, from sharp-libvips v1.3.4's own inputs. That method
reproduces the 1.3.3 supplement byte for byte.
- PROVENANCE.md records:
- the 27 upstream archives and five build-time patches, by sha256;
- the librsvg 2.63.2 crate reproduction (cargo 1.99.0; Cargo.lock 5723e14c…);
- rustc 75a75c3e…;
- every change from 1.3.3.
- Notable: sharp-libvips v1.3.4 now states cairo is used under MPL 1.1, not MPL 2.0. cairo ships
that text itself, so the standard MPL 2.0 text is no longer added for cairo; selectors still
carries it.
- No legal conclusion: the LGPL and MPL source-availability determination stays open, as for 1.3.3.
- The 1.3.3 supplement is unchanged, and still proven: module-pack keeps sharp 0.35.4 as a test-only
devDependency alias (`sharp-0.35.4`). Each supplement is pinned against its real installed
libvips, and each matches only its own.
- Native proof fixture: sharp 0.35.4 → 0.35.5. The closure has the same shape: sharp, @img/colour,
detect-libc, semver, and @img/sharp-linux-x64 0.35.5 with @img/sharp-libvips-linux-x64 1.3.4.
The runtime read from the binaries is unchanged: Node-API 9, glibc >= 2.28, x86-64.
- Docs: the module guide's note on available supplements.
No version bump, no publication, no tag.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
24 lines
1.4 KiB
Plaintext
24 lines
1.4 KiB
Plaintext
Additional IP Rights Grant (Patents)
|
|
------------------------------------
|
|
|
|
"These implementations" means the copyrightable works that implement the WebM
|
|
codecs distributed by Google as part of the WebM Project.
|
|
|
|
Google hereby grants to you a perpetual, worldwide, non-exclusive, no-charge,
|
|
royalty-free, irrevocable (except as stated in this section) patent license to
|
|
make, have made, use, offer to sell, sell, import, transfer, and otherwise
|
|
run, modify and propagate the contents of these implementations of WebM, where
|
|
such license applies only to those patent claims, both currently owned by
|
|
Google and acquired in the future, licensable by Google that are necessarily
|
|
infringed by these implementations of WebM. This grant does not include claims
|
|
that would be infringed only as a consequence of further modification of these
|
|
implementations. If you or your agent or exclusive licensee institute or order
|
|
or agree to the institution of patent litigation or any other patent
|
|
enforcement activity against any entity (including a cross-claim or
|
|
counterclaim in a lawsuit) alleging that any of these implementations of WebM
|
|
or any code incorporated within any of these implementations of WebM
|
|
constitute direct or contributory patent infringement, or inducement of
|
|
patent infringement, then any patent rights granted to you under this License
|
|
for these implementations of WebM shall terminate as of the date such
|
|
litigation is filed.
|