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]>
34 lines
1.5 KiB
Plaintext
34 lines
1.5 KiB
Plaintext
Cairo is free software.
|
|
|
|
Every source file in the implementation[*] of cairo is available to be
|
|
redistributed and/or modified under the terms of either the GNU Lesser
|
|
General Public License (LGPL) version 2.1 or the Mozilla Public
|
|
License (MPL) version 1.1. Some files are available under more
|
|
liberal terms, but we believe that in all cases, each file may be used
|
|
under either the LGPL or the MPL.
|
|
|
|
See the following files in this directory for the precise terms and
|
|
conditions of either license:
|
|
|
|
COPYING-LGPL-2.1
|
|
COPYING-MPL-1.1
|
|
|
|
Please see each file in the implementation for copyright and licensing
|
|
information, (in the opening comment of each file).
|
|
|
|
[*] The implementation of cairo is contained entirely within the "src"
|
|
directory of the cairo source distribution. There are other components
|
|
of the cairo source distribution (such as the "test", "util", and "perf")
|
|
that are auxiliary to the library itself. None of the source code in these
|
|
directories contributes to a build of the cairo library itself, (libcairo.so
|
|
or cairo.dll or similar).
|
|
|
|
These auxiliary components are also free software, but may be under
|
|
different license terms than cairo itself. For example, most of the
|
|
test cases in the perf and test directories are made available under
|
|
an MIT license to simplify any use of this code for reference purposes
|
|
in using cairo itself. Other files might be available under the GNU
|
|
General Public License (GPL), for example. Again, please see the COPYING
|
|
file under each directory and the opening comment of each file for copyright
|
|
and licensing information.
|