qpdf-node 0.0.0-stage → 0.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,765 @@
1
+ # Third-party notices
2
+
3
+ qpdf-node's own source (MIT, see `LICENSE`) links the third-party software below.
4
+ This file is generated by `scripts/generate-third-party-notices.mjs`; do not edit it by hand.
5
+
6
+ | Component | Version | License | Where it ends up |
7
+ | --- | --- | --- | --- |
8
+ | [qpdf](https://github.com/qpdf/qpdf) | v12.4.2 (4eba95899886e851cc41d76886483b347612f2a8) | Apache-2.0 | statically linked into the Node addon and the WebAssembly module |
9
+ | [zlib](https://github.com/madler/zlib) | v1.3.1 (51b7f2abdade71cd9bb0e7a373ef2610ec6f9daf) | zlib License | statically linked into both |
10
+ | [libjpeg-turbo](https://github.com/libjpeg-turbo/libjpeg-turbo) | 3.1.4.1 (9217719d3a58633923b096af4c1d50d304768a64) | IJG License and BSD-3-Clause (zlib License for part of the code) | statically linked into both |
11
+ | [node-addon-api](https://github.com/nodejs/node-addon-api) | 8.9.2 | MIT | header-only; compiled into the Node addon |
12
+ | [Node-API headers](https://github.com/nodejs/node-api-headers) | via cmake-js | MIT | headers compiled into the Node addon |
13
+ | [Emscripten](https://github.com/emscripten-core/emscripten) runtime, musl libc, LLVM libc++ | the toolchain used for the build | MIT / UIUC, MIT, Apache-2.0 with LLVM exceptions | linked into the WebAssembly module only |
14
+
15
+ The sources are fetched by CMake at the pinned commits above; none is copied into this repository.
16
+ qpdf has no runtime dependency on OpenSSL or GnuTLS here: the build uses qpdf's built-in crypto code
17
+ (AES, RC4, MD5, SHA-2), covered by the qpdf notices below.
18
+
19
+ For the WebAssembly module, whoever distributes the built `.mjs`/`.wasm` must also ship the license
20
+ texts of the Emscripten toolchain that produced it (Emscripten's `LICENSE` and the musl and LLVM
21
+ libc++ licenses in the SDK), which are not reproduced here.
22
+
23
+ The package.json license field, `MIT AND Apache-2.0`, reflects this repository's MIT source plus
24
+ the Apache-2.0 qpdf code in the compiled addon; the other components keep the permissive licenses
25
+ quoted below.
26
+
27
+ ## qpdf v12.4.2 (Apache-2.0)
28
+
29
+ qpdf is distributed under the Apache License, version 2.0. Its source is available at
30
+ https://github.com/qpdf/qpdf (commit 4eba95899886e851cc41d76886483b347612f2a8).
31
+
32
+ ### qpdf NOTICE
33
+
34
+ qpdf is copyright (c) 2005-2021 Jay Berkenbilt, 2022-2026 Jay Berkenbilt and Manfred Holger
35
+
36
+ Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
37
+
38
+ http://www.apache.org/licenses/LICENSE-2.0
39
+
40
+ Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
41
+
42
+ Versions of qpdf prior to version 7 were released under the terms of version 2.0 of the Artistic License. At your option, you may continue to consider qpdf to be licensed under those terms. Please see the manual for additional information.
43
+
44
+ The qpdf distribution includes a copy of [qtest](https://qtest.sourceforge.io), which is released under the terms of the [version 2.0 of the Artistic license](https://opensource.org/licenses/Artistic-2.0), which can be found at https://opensource.org/licenses/Artistic-2.0.
45
+
46
+ The Rijndael encryption implementation used as the basis for AES encryption and decryption support comes from Philip J. Erdelsky's public domain implementation. The files `libqpdf/rijndael.cc` and `libqpdf/qpdf/rijndael.h` remain in the public domain. They were obtained from
47
+ * http://www.efgh.com/software/rijndael.htm
48
+ * http://www.efgh.com/software/rijndael.txt
49
+
50
+ The embedded sha2 code comes from sphlib 3.0
51
+ * http://www.saphir2.com/sphlib/
52
+
53
+ That code has the following license:
54
+ ```
55
+ Copyright (c) 2007-2011 Projet RNRT SAPHIR
56
+
57
+ Permission is hereby granted, free of charge, to any person obtaining
58
+ a copy of this software and associated documentation files (the
59
+ "Software"), to deal in the Software without restriction, including
60
+ without limitation the rights to use, copy, modify, merge, publish,
61
+ distribute, sublicense, and/or sell copies of the Software, and to
62
+ permit persons to whom the Software is furnished to do so, subject to
63
+ the following conditions:
64
+
65
+ The above copyright notice and this permission notice shall be included
66
+ in all copies or substantial portions of the Software.
67
+
68
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
69
+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
70
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
71
+ IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
72
+ CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
73
+ TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
74
+ SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
75
+ ```
76
+
77
+ ### Apache License 2.0 (qpdf LICENSE.txt)
78
+
79
+ ```text
80
+
81
+ Apache License
82
+ Version 2.0, January 2004
83
+ http://www.apache.org/licenses/
84
+
85
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
86
+
87
+ 1. Definitions.
88
+
89
+ "License" shall mean the terms and conditions for use, reproduction,
90
+ and distribution as defined by Sections 1 through 9 of this document.
91
+
92
+ "Licensor" shall mean the copyright owner or entity authorized by
93
+ the copyright owner that is granting the License.
94
+
95
+ "Legal Entity" shall mean the union of the acting entity and all
96
+ other entities that control, are controlled by, or are under common
97
+ control with that entity. For the purposes of this definition,
98
+ "control" means (i) the power, direct or indirect, to cause the
99
+ direction or management of such entity, whether by contract or
100
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
101
+ outstanding shares, or (iii) beneficial ownership of such entity.
102
+
103
+ "You" (or "Your") shall mean an individual or Legal Entity
104
+ exercising permissions granted by this License.
105
+
106
+ "Source" form shall mean the preferred form for making modifications,
107
+ including but not limited to software source code, documentation
108
+ source, and configuration files.
109
+
110
+ "Object" form shall mean any form resulting from mechanical
111
+ transformation or translation of a Source form, including but
112
+ not limited to compiled object code, generated documentation,
113
+ and conversions to other media types.
114
+
115
+ "Work" shall mean the work of authorship, whether in Source or
116
+ Object form, made available under the License, as indicated by a
117
+ copyright notice that is included in or attached to the work
118
+ (an example is provided in the Appendix below).
119
+
120
+ "Derivative Works" shall mean any work, whether in Source or Object
121
+ form, that is based on (or derived from) the Work and for which the
122
+ editorial revisions, annotations, elaborations, or other modifications
123
+ represent, as a whole, an original work of authorship. For the purposes
124
+ of this License, Derivative Works shall not include works that remain
125
+ separable from, or merely link (or bind by name) to the interfaces of,
126
+ the Work and Derivative Works thereof.
127
+
128
+ "Contribution" shall mean any work of authorship, including
129
+ the original version of the Work and any modifications or additions
130
+ to that Work or Derivative Works thereof, that is intentionally
131
+ submitted to Licensor for inclusion in the Work by the copyright owner
132
+ or by an individual or Legal Entity authorized to submit on behalf of
133
+ the copyright owner. For the purposes of this definition, "submitted"
134
+ means any form of electronic, verbal, or written communication sent
135
+ to the Licensor or its representatives, including but not limited to
136
+ communication on electronic mailing lists, source code control systems,
137
+ and issue tracking systems that are managed by, or on behalf of, the
138
+ Licensor for the purpose of discussing and improving the Work, but
139
+ excluding communication that is conspicuously marked or otherwise
140
+ designated in writing by the copyright owner as "Not a Contribution."
141
+
142
+ "Contributor" shall mean Licensor and any individual or Legal Entity
143
+ on behalf of whom a Contribution has been received by Licensor and
144
+ subsequently incorporated within the Work.
145
+
146
+ 2. Grant of Copyright License. Subject to the terms and conditions of
147
+ this License, each Contributor hereby grants to You a perpetual,
148
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
149
+ copyright license to reproduce, prepare Derivative Works of,
150
+ publicly display, publicly perform, sublicense, and distribute the
151
+ Work and such Derivative Works in Source or Object form.
152
+
153
+ 3. Grant of Patent License. Subject to the terms and conditions of
154
+ this License, each Contributor hereby grants to You a perpetual,
155
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
156
+ (except as stated in this section) patent license to make, have made,
157
+ use, offer to sell, sell, import, and otherwise transfer the Work,
158
+ where such license applies only to those patent claims licensable
159
+ by such Contributor that are necessarily infringed by their
160
+ Contribution(s) alone or by combination of their Contribution(s)
161
+ with the Work to which such Contribution(s) was submitted. If You
162
+ institute patent litigation against any entity (including a
163
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
164
+ or a Contribution incorporated within the Work constitutes direct
165
+ or contributory patent infringement, then any patent licenses
166
+ granted to You under this License for that Work shall terminate
167
+ as of the date such litigation is filed.
168
+
169
+ 4. Redistribution. You may reproduce and distribute copies of the
170
+ Work or Derivative Works thereof in any medium, with or without
171
+ modifications, and in Source or Object form, provided that You
172
+ meet the following conditions:
173
+
174
+ (a) You must give any other recipients of the Work or
175
+ Derivative Works a copy of this License; and
176
+
177
+ (b) You must cause any modified files to carry prominent notices
178
+ stating that You changed the files; and
179
+
180
+ (c) You must retain, in the Source form of any Derivative Works
181
+ that You distribute, all copyright, patent, trademark, and
182
+ attribution notices from the Source form of the Work,
183
+ excluding those notices that do not pertain to any part of
184
+ the Derivative Works; and
185
+
186
+ (d) If the Work includes a "NOTICE" text file as part of its
187
+ distribution, then any Derivative Works that You distribute must
188
+ include a readable copy of the attribution notices contained
189
+ within such NOTICE file, excluding those notices that do not
190
+ pertain to any part of the Derivative Works, in at least one
191
+ of the following places: within a NOTICE text file distributed
192
+ as part of the Derivative Works; within the Source form or
193
+ documentation, if provided along with the Derivative Works; or,
194
+ within a display generated by the Derivative Works, if and
195
+ wherever such third-party notices normally appear. The contents
196
+ of the NOTICE file are for informational purposes only and
197
+ do not modify the License. You may add Your own attribution
198
+ notices within Derivative Works that You distribute, alongside
199
+ or as an addendum to the NOTICE text from the Work, provided
200
+ that such additional attribution notices cannot be construed
201
+ as modifying the License.
202
+
203
+ You may add Your own copyright statement to Your modifications and
204
+ may provide additional or different license terms and conditions
205
+ for use, reproduction, or distribution of Your modifications, or
206
+ for any such Derivative Works as a whole, provided Your use,
207
+ reproduction, and distribution of the Work otherwise complies with
208
+ the conditions stated in this License.
209
+
210
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
211
+ any Contribution intentionally submitted for inclusion in the Work
212
+ by You to the Licensor shall be under the terms and conditions of
213
+ this License, without any additional terms or conditions.
214
+ Notwithstanding the above, nothing herein shall supersede or modify
215
+ the terms of any separate license agreement you may have executed
216
+ with Licensor regarding such Contributions.
217
+
218
+ 6. Trademarks. This License does not grant permission to use the trade
219
+ names, trademarks, service marks, or product names of the Licensor,
220
+ except as required for reasonable and customary use in describing the
221
+ origin of the Work and reproducing the content of the NOTICE file.
222
+
223
+ 7. Disclaimer of Warranty. Unless required by applicable law or
224
+ agreed to in writing, Licensor provides the Work (and each
225
+ Contributor provides its Contributions) on an "AS IS" BASIS,
226
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
227
+ implied, including, without limitation, any warranties or conditions
228
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
229
+ PARTICULAR PURPOSE. You are solely responsible for determining the
230
+ appropriateness of using or redistributing the Work and assume any
231
+ risks associated with Your exercise of permissions under this License.
232
+
233
+ 8. Limitation of Liability. In no event and under no legal theory,
234
+ whether in tort (including negligence), contract, or otherwise,
235
+ unless required by applicable law (such as deliberate and grossly
236
+ negligent acts) or agreed to in writing, shall any Contributor be
237
+ liable to You for damages, including any direct, indirect, special,
238
+ incidental, or consequential damages of any character arising as a
239
+ result of this License or out of the use or inability to use the
240
+ Work (including but not limited to damages for loss of goodwill,
241
+ work stoppage, computer failure or malfunction, or any and all
242
+ other commercial damages or losses), even if such Contributor
243
+ has been advised of the possibility of such damages.
244
+
245
+ 9. Accepting Warranty or Additional Liability. While redistributing
246
+ the Work or Derivative Works thereof, You may choose to offer,
247
+ and charge a fee for, acceptance of support, warranty, indemnity,
248
+ or other liability obligations and/or rights consistent with this
249
+ License. However, in accepting such obligations, You may act only
250
+ on Your own behalf and on Your sole responsibility, not on behalf
251
+ of any other Contributor, and only if You agree to indemnify,
252
+ defend, and hold each Contributor harmless for any liability
253
+ incurred by, or claims asserted against, such Contributor by reason
254
+ of your accepting any such warranty or additional liability.
255
+
256
+ END OF TERMS AND CONDITIONS
257
+
258
+ APPENDIX: How to apply the Apache License to your work.
259
+
260
+ To apply the Apache License to your work, attach the following
261
+ boilerplate notice, with the fields enclosed by brackets "[]"
262
+ replaced with your own identifying information. (Don't include
263
+ the brackets!) The text should be enclosed in the appropriate
264
+ comment syntax for the file format. We also recommend that a
265
+ file or class name and description of purpose be included on the
266
+ same "printed page" as the copyright notice for easier
267
+ identification within third-party archives.
268
+
269
+ Copyright [yyyy] [name of copyright owner]
270
+
271
+ Licensed under the Apache License, Version 2.0 (the "License");
272
+ you may not use this file except in compliance with the License.
273
+ You may obtain a copy of the License at
274
+
275
+ http://www.apache.org/licenses/LICENSE-2.0
276
+
277
+ Unless required by applicable law or agreed to in writing, software
278
+ distributed under the License is distributed on an "AS IS" BASIS,
279
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
280
+ See the License for the specific language governing permissions and
281
+ limitations under the License.
282
+ ```
283
+
284
+ ## zlib v1.3.1
285
+
286
+ ```text
287
+ Copyright notice:
288
+
289
+ (C) 1995-2022 Jean-loup Gailly and Mark Adler
290
+
291
+ This software is provided 'as-is', without any express or implied
292
+ warranty. In no event will the authors be held liable for any damages
293
+ arising from the use of this software.
294
+
295
+ Permission is granted to anyone to use this software for any purpose,
296
+ including commercial applications, and to alter it and redistribute it
297
+ freely, subject to the following restrictions:
298
+
299
+ 1. The origin of this software must not be misrepresented; you must not
300
+ claim that you wrote the original software. If you use this software
301
+ in a product, an acknowledgment in the product documentation would be
302
+ appreciated but is not required.
303
+ 2. Altered source versions must be plainly marked as such, and must not be
304
+ misrepresented as being the original software.
305
+ 3. This notice may not be removed or altered from any source distribution.
306
+
307
+ Jean-loup Gailly Mark Adler
308
+ jloup@gzip.org madler@alumni.caltech.edu
309
+ ```
310
+
311
+ The notice in zlib's README:
312
+
313
+ ```text
314
+ (C) 1995-2024 Jean-loup Gailly and Mark Adler
315
+
316
+ This software is provided 'as-is', without any express or implied
317
+ warranty. In no event will the authors be held liable for any damages
318
+ arising from the use of this software.
319
+
320
+ Permission is granted to anyone to use this software for any purpose,
321
+ including commercial applications, and to alter it and redistribute it
322
+ freely, subject to the following restrictions:
323
+
324
+ 1. The origin of this software must not be misrepresented; you must not
325
+ claim that you wrote the original software. If you use this software
326
+ in a product, an acknowledgment in the product documentation would be
327
+ appreciated but is not required.
328
+ 2. Altered source versions must be plainly marked as such, and must not be
329
+ misrepresented as being the original software.
330
+ 3. This notice may not be removed or altered from any source distribution.
331
+
332
+ Jean-loup Gailly Mark Adler
333
+ jloup@gzip.org madler@alumni.caltech.edu
334
+
335
+ If you use the zlib library in a product, we would appreciate *not* receiving
336
+ lengthy legal documents to sign. The sources are provided for free but without
337
+ warranty of any kind. The library has been entirely written by Jean-loup
338
+ Gailly and Mark Adler; it does not include third-party code. We make all
339
+ contributions to and distributions of this project solely in our personal
340
+ capacity, and are not conveying any rights to any intellectual property of
341
+ any third parties.
342
+
343
+ If you redistribute modified sources, we would appreciate that you include in
344
+ the file ChangeLog history information documenting your changes. Please read
345
+ the FAQ for more information on the distribution of modified source versions.
346
+ ```
347
+
348
+ ## libjpeg-turbo 3.1.4.1
349
+
350
+ ### LICENSE.md
351
+
352
+ libjpeg-turbo Licenses
353
+ ======================
354
+
355
+ libjpeg-turbo is covered by two compatible BSD-style open source licenses:
356
+
357
+ - The IJG (Independent JPEG Group) License, which is listed in
358
+ [README.ijg](README.ijg)
359
+
360
+ This license applies to the libjpeg API library and associated programs,
361
+ including any code inherited from libjpeg and any modifications to that
362
+ code. Note that the libjpeg-turbo SIMD source code bears the
363
+ [zlib License](https://opensource.org/licenses/Zlib), but in the context of
364
+ the overall libjpeg API library, the terms of the zlib License are subsumed
365
+ by the terms of the IJG License.
366
+
367
+ - The Modified (3-clause) BSD License, which is listed below
368
+
369
+ This license applies to the TurboJPEG API library and associated programs, as
370
+ well as the build system. Note that the TurboJPEG API library wraps the
371
+ libjpeg API library, so in the context of the overall TurboJPEG API library,
372
+ both the terms of the IJG License and the terms of the Modified (3-clause)
373
+ BSD License apply.
374
+
375
+
376
+ Complying with the libjpeg-turbo Licenses
377
+ =========================================
378
+
379
+ This section provides a roll-up of the libjpeg-turbo licensing terms, to the
380
+ best of our understanding. This is not a license in and of itself. It is
381
+ intended solely for clarification.
382
+
383
+ 1. If you are distributing a modified version of the libjpeg-turbo source,
384
+ then:
385
+
386
+ 1. You cannot alter or remove any existing copyright or license notices
387
+ from the source.
388
+
389
+ **Origin**
390
+ - Clause 1 of the IJG License
391
+ - Clause 1 of the Modified BSD License
392
+ - Clauses 1 and 3 of the zlib License
393
+
394
+ 2. You must add your own copyright notice to the header of each source
395
+ file you modified, so others can tell that you modified that file. (If
396
+ there is not an existing copyright header in that file, then you can
397
+ simply add a notice stating that you modified the file.)
398
+
399
+ **Origin**
400
+ - Clause 1 of the IJG License
401
+ - Clause 2 of the zlib License
402
+
403
+ 3. You must include the IJG README file, and you must not alter any of the
404
+ copyright or license text in that file.
405
+
406
+ **Origin**
407
+ - Clause 1 of the IJG License
408
+
409
+ 2. If you are distributing only libjpeg-turbo binaries without the source, or
410
+ if you are distributing an application that statically links with
411
+ libjpeg-turbo, then:
412
+
413
+ 1. Your product documentation must include a message stating:
414
+
415
+ This software is based in part on the work of the Independent JPEG
416
+ Group.
417
+
418
+ **Origin**
419
+ - Clause 2 of the IJG license
420
+
421
+ 2. If your binary distribution includes or uses the TurboJPEG API, then
422
+ your product documentation must include the text of the Modified BSD
423
+ License (see below.)
424
+
425
+ **Origin**
426
+ - Clause 2 of the Modified BSD License
427
+
428
+ 3. You cannot use the name of the IJG or The libjpeg-turbo Project or the
429
+ contributors thereof in advertising, publicity, etc.
430
+
431
+ **Origin**
432
+ - IJG License
433
+ - Clause 3 of the Modified BSD License
434
+
435
+ 4. The IJG and The libjpeg-turbo Project do not warrant libjpeg-turbo to be
436
+ free of defects, nor do we accept any liability for undesirable
437
+ consequences resulting from your use of the software.
438
+
439
+ **Origin**
440
+ - IJG License
441
+ - Modified BSD License
442
+ - zlib License
443
+
444
+
445
+ The Modified (3-clause) BSD License
446
+ ===================================
447
+
448
+ Copyright (C) 2009-2026 D. R. Commander. All Rights Reserved.<br>
449
+ Copyright (C) 2015 Viktor Szathmáry. All Rights Reserved.
450
+
451
+ Redistribution and use in source and binary forms, with or without
452
+ modification, are permitted provided that the following conditions are met:
453
+
454
+ - Redistributions of source code must retain the above copyright notice,
455
+ this list of conditions and the following disclaimer.
456
+ - Redistributions in binary form must reproduce the above copyright notice,
457
+ this list of conditions and the following disclaimer in the documentation
458
+ and/or other materials provided with the distribution.
459
+ - Neither the name of the libjpeg-turbo Project nor the names of its
460
+ contributors may be used to endorse or promote products derived from this
461
+ software without specific prior written permission.
462
+
463
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS",
464
+ AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
465
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
466
+ ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE
467
+ LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
468
+ CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
469
+ SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
470
+ INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
471
+ CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
472
+ ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
473
+ POSSIBILITY OF SUCH DAMAGE.
474
+
475
+
476
+ Why Two Licenses?
477
+ =================
478
+
479
+ The zlib License could have been used instead of the Modified (3-clause) BSD
480
+ License, and since the IJG License effectively subsumes the distribution
481
+ conditions of the zlib License, this would have effectively placed
482
+ libjpeg-turbo binary distributions under the IJG License. However, the IJG
483
+ License specifically refers to the Independent JPEG Group and does not extend
484
+ attribution and endorsement protections to other entities. Thus, it was
485
+ desirable to choose a license that granted us the same protections for new code
486
+ that were granted to the IJG for code derived from their software.
487
+
488
+ ### README.ijg
489
+
490
+ ```text
491
+ libjpeg-turbo note: This file has been modified by The libjpeg-turbo Project
492
+ to include only information relevant to libjpeg-turbo, to wordsmith certain
493
+ sections, and to remove impolitic language that existed in the libjpeg v8
494
+ README. It is included only for reference. Please see README.md for
495
+ information specific to libjpeg-turbo.
496
+
497
+
498
+ The Independent JPEG Group's JPEG software
499
+ ==========================================
500
+
501
+ This distribution contains a release of the Independent JPEG Group's free JPEG
502
+ software. You are welcome to redistribute this software and to use it for any
503
+ purpose, subject to the conditions under LEGAL ISSUES, below.
504
+
505
+ This software is the work of Tom Lane, Guido Vollbeding, Philip Gladstone,
506
+ Bill Allombert, Jim Boucher, Lee Crocker, Bob Friesenhahn, Ben Jackson,
507
+ Julian Minguillon, Luis Ortiz, George Phillips, Davide Rossi, Ge' Weijers,
508
+ and other members of the Independent JPEG Group.
509
+
510
+ IJG is not affiliated with the ISO/IEC JTC1/SC29/WG1 standards committee
511
+ (also known as JPEG, together with ITU-T SG16).
512
+
513
+
514
+ DOCUMENTATION ROADMAP
515
+ =====================
516
+
517
+ This file contains the following sections:
518
+
519
+ OVERVIEW General description of JPEG and the IJG software.
520
+ LEGAL ISSUES Copyright, lack of warranty, terms of distribution.
521
+ REFERENCES Where to learn more about JPEG.
522
+ ARCHIVE LOCATIONS Where to find newer versions of this software.
523
+ FILE FORMAT WARS Software *not* to get.
524
+ TO DO Plans for future IJG releases.
525
+
526
+ Other documentation files in the distribution are:
527
+
528
+ User documentation:
529
+ doc/usage.txt Usage instructions for cjpeg, djpeg, jpegtran,
530
+ rdjpgcom, and wrjpgcom.
531
+ doc/*.1 Unix-style man pages for programs (same info as
532
+ usage.txt).
533
+ doc/wizard.txt Advanced usage instructions for JPEG wizards only.
534
+ doc/change.log Version-to-version change highlights.
535
+ Programmer and internal documentation:
536
+ doc/libjpeg.txt How to use the JPEG library in your own programs.
537
+ src/example.c Sample code for calling the JPEG library.
538
+ doc/structure.txt Overview of the JPEG library's internal structure.
539
+ doc/coderules.txt Coding style rules --- please read if you contribute
540
+ code.
541
+
542
+ Please read at least usage.txt. Some information can also be found in the JPEG
543
+ FAQ (Frequently Asked Questions) article. See ARCHIVE LOCATIONS below to find
544
+ out where to obtain the FAQ article.
545
+
546
+ If you want to understand how the JPEG code works, we suggest reading one or
547
+ more of the REFERENCES, then looking at the documentation files (in roughly
548
+ the order listed) before diving into the code.
549
+
550
+
551
+ OVERVIEW
552
+ ========
553
+
554
+ This package contains C software to implement JPEG image encoding, decoding,
555
+ and transcoding. JPEG (pronounced "jay-peg") is a standardized compression
556
+ method for full-color and grayscale images. JPEG's strong suit is compressing
557
+ photographic images or other types of images that have smooth color and
558
+ brightness transitions between neighboring pixels. Images with sharp lines or
559
+ other abrupt features may not compress well with JPEG, and a higher JPEG
560
+ quality may have to be used to avoid visible compression artifacts with such
561
+ images.
562
+
563
+ JPEG is normally lossy, meaning that the output pixels are not necessarily
564
+ identical to the input pixels. However, on photographic content and other
565
+ "smooth" images, very good compression ratios can be obtained with no visible
566
+ compression artifacts, and extremely high compression ratios are possible if
567
+ you are willing to sacrifice image quality (by reducing the "quality" setting
568
+ in the compressor.)
569
+
570
+ This software implements JPEG baseline, extended-sequential, progressive, and
571
+ lossless compression processes. Provision is made for supporting all variants
572
+ of these processes, although some uncommon parameter settings aren't
573
+ implemented yet. We have made no provision for supporting the hierarchical
574
+ processes defined in the standard.
575
+
576
+ We provide a set of library routines for reading and writing JPEG image files,
577
+ plus two sample applications "cjpeg" and "djpeg", which use the library to
578
+ perform conversion between JPEG and some other popular image file formats.
579
+ The library is intended to be reused in other applications.
580
+
581
+ In order to support file conversion and viewing software, we have included
582
+ considerable functionality beyond the bare JPEG coding/decoding capability;
583
+ for example, the color quantization modules are not strictly part of JPEG
584
+ decoding, but they are essential for output to colormapped file formats. These
585
+ extra functions can be compiled out of the library if not required for a
586
+ particular application.
587
+
588
+ We have also included "jpegtran", a utility for lossless transcoding between
589
+ different JPEG processes, and "rdjpgcom" and "wrjpgcom", two simple
590
+ applications for inserting and extracting textual comments in JFIF files.
591
+
592
+ The emphasis in designing this software has been on achieving portability and
593
+ flexibility, while also making it fast enough to be useful. In particular,
594
+ the software is not intended to be read as a tutorial on JPEG. (See the
595
+ REFERENCES section for introductory material.) Rather, it is intended to
596
+ be reliable, portable, industrial-strength code. We do not claim to have
597
+ achieved that goal in every aspect of the software, but we strive for it.
598
+
599
+ We welcome the use of this software as a component of commercial products.
600
+ No royalty is required, but we do ask for an acknowledgement in product
601
+ documentation, as described under LEGAL ISSUES.
602
+
603
+
604
+ LEGAL ISSUES
605
+ ============
606
+
607
+ In plain English:
608
+
609
+ 1. We don't promise that this software works. (But if you find any bugs,
610
+ please let us know!)
611
+ 2. You can use this software for whatever you want. You don't have to pay us.
612
+ 3. You may not pretend that you wrote this software. If you use it in a
613
+ program, you must acknowledge somewhere in your documentation that
614
+ you've used the IJG code.
615
+
616
+ In legalese:
617
+
618
+ The authors make NO WARRANTY or representation, either express or implied,
619
+ with respect to this software, its quality, accuracy, merchantability, or
620
+ fitness for a particular purpose. This software is provided "AS IS", and you,
621
+ its user, assume the entire risk as to its quality and accuracy.
622
+
623
+ This software is copyright (C) 1991-2020, Thomas G. Lane, Guido Vollbeding.
624
+ All Rights Reserved except as specified below.
625
+
626
+ Permission is hereby granted to use, copy, modify, and distribute this
627
+ software (or portions thereof) for any purpose, without fee, subject to these
628
+ conditions:
629
+ (1) If any part of the source code for this software is distributed, then this
630
+ README file must be included, with this copyright and no-warranty notice
631
+ unaltered; and any additions, deletions, or changes to the original files
632
+ must be clearly indicated in accompanying documentation.
633
+ (2) If only executable code is distributed, then the accompanying
634
+ documentation must state that "this software is based in part on the work of
635
+ the Independent JPEG Group".
636
+ (3) Permission for use of this software is granted only if the user accepts
637
+ full responsibility for any undesirable consequences; the authors accept
638
+ NO LIABILITY for damages of any kind.
639
+
640
+ These conditions apply to any software derived from or based on the IJG code,
641
+ not just to the unmodified library. If you use our work, you ought to
642
+ acknowledge us.
643
+
644
+ Permission is NOT granted for the use of any IJG author's name or company name
645
+ in advertising or publicity relating to this software or products derived from
646
+ it. This software may be referred to only as "the Independent JPEG Group's
647
+ software".
648
+
649
+ We specifically permit and encourage the use of this software as the basis of
650
+ commercial products, provided that all warranty or liability claims are
651
+ assumed by the product vendor.
652
+
653
+
654
+ REFERENCES
655
+ ==========
656
+
657
+ We recommend reading one or more of these references before trying to
658
+ understand the innards of the JPEG software.
659
+
660
+ The best short technical introduction to the JPEG compression algorithm is
661
+ Wallace, Gregory K. "The JPEG Still Picture Compression Standard",
662
+ Communications of the ACM, April 1991 (vol. 34 no. 4), pp. 30-44.
663
+ (Adjacent articles in that issue discuss MPEG motion picture compression,
664
+ applications of JPEG, and related topics.) If you don't have the CACM issue
665
+ handy, a PDF file containing a revised version of Wallace's article is
666
+ available at http://www.ijg.org/files/Wallace.JPEG.pdf. The file (actually
667
+ a preprint for an article that appeared in IEEE Trans. Consumer Electronics)
668
+ omits the sample images that appeared in CACM, but it includes corrections
669
+ and some added material. Note: the Wallace article is copyright ACM and IEEE,
670
+ and it may not be used for commercial purposes.
671
+
672
+ A somewhat less technical, more leisurely introduction to JPEG can be found in
673
+ "The Data Compression Book" by Mark Nelson and Jean-loup Gailly, published by
674
+ M&T Books (New York), 2nd ed. 1996, ISBN 1-55851-434-1. This book provides
675
+ good explanations and example C code for a multitude of compression methods
676
+ including JPEG. It is an excellent source if you are comfortable reading C
677
+ code but don't know much about data compression in general. The book's JPEG
678
+ sample code is far from industrial-strength, but when you are ready to look
679
+ at a full implementation, you've got one here...
680
+
681
+ The best currently available description of JPEG is the textbook "JPEG Still
682
+ Image Data Compression Standard" by William B. Pennebaker and Joan L.
683
+ Mitchell, published by Van Nostrand Reinhold, 1993, ISBN 0-442-01272-1.
684
+ Price US$59.95, 638 pp. The book includes the complete text of the ISO JPEG
685
+ standards (DIS 10918-1 and draft DIS 10918-2).
686
+
687
+ The original JPEG standard is divided into two parts, Part 1 being the actual
688
+ specification, while Part 2 covers compliance testing methods. Part 1 is
689
+ titled "Digital Compression and Coding of Continuous-tone Still Images,
690
+ Part 1: Requirements and guidelines" and has document numbers ISO/IEC IS
691
+ 10918-1, ITU-T T.81. Part 2 is titled "Digital Compression and Coding of
692
+ Continuous-tone Still Images, Part 2: Compliance testing" and has document
693
+ numbers ISO/IEC IS 10918-2, ITU-T T.83.
694
+
695
+ The JPEG standard does not specify all details of an interchangeable file
696
+ format. For the omitted details, we follow the "JFIF" conventions, revision
697
+ 1.02. JFIF version 1 has been adopted as ISO/IEC 10918-5 (05/2013) and
698
+ Recommendation ITU-T T.871 (05/2011): Information technology - Digital
699
+ compression and coding of continuous-tone still images: JPEG File Interchange
700
+ Format (JFIF). It is available as a free download in PDF file format from
701
+ https://www.iso.org/standard/54989.html and http://www.itu.int/rec/T-REC-T.871.
702
+ A PDF file of the older JFIF 1.02 specification is available at
703
+ http://www.w3.org/Graphics/JPEG/jfif3.pdf.
704
+
705
+ The TIFF 6.0 file format specification can be obtained from
706
+ http://mirrors.ctan.org/graphics/tiff/TIFF6.ps.gz. The JPEG incorporation
707
+ scheme found in the TIFF 6.0 spec of 3-June-92 has a number of serious
708
+ problems. IJG does not recommend use of the TIFF 6.0 design (TIFF Compression
709
+ tag 6). Instead, we recommend the JPEG design proposed by TIFF Technical Note
710
+ #2 (Compression tag 7). Copies of this Note can be obtained from
711
+ http://www.ijg.org/files/. It is expected that the next revision
712
+ of the TIFF spec will replace the 6.0 JPEG design with the Note's design.
713
+ Although IJG's own code does not support TIFF/JPEG, the free libtiff library
714
+ uses our library to implement TIFF/JPEG per the Note.
715
+
716
+
717
+ ARCHIVE LOCATIONS
718
+ =================
719
+
720
+ The "official" archive site for this software is www.ijg.org.
721
+ The most recent released version can always be found there in
722
+ directory "files".
723
+
724
+ The JPEG FAQ (Frequently Asked Questions) article is a source of some
725
+ general information about JPEG. It is available at
726
+ http://www.faqs.org/faqs/jpeg-faq.
727
+
728
+
729
+ FILE FORMAT COMPATIBILITY
730
+ =========================
731
+
732
+ This software implements ITU T.81 | ISO/IEC 10918 with some extensions from
733
+ ITU T.871 | ISO/IEC 10918-5 (JPEG File Interchange Format-- see REFERENCES).
734
+ Informally, the term "JPEG image" or "JPEG file" most often refers to JFIF or
735
+ a subset thereof, but there are other formats containing the name "JPEG" that
736
+ are incompatible with the original JPEG standard or with JFIF (for instance,
737
+ JPEG 2000 and JPEG XR). This software therefore does not support these
738
+ formats. Indeed, one of the original reasons for developing this free software
739
+ was to help force convergence on a common, interoperable format standard for
740
+ JPEG files.
741
+
742
+ JFIF is a minimal or "low end" representation. TIFF/JPEG (TIFF revision 6.0 as
743
+ modified by TIFF Technical Note #2) can be used for "high end" applications
744
+ that need to record a lot of additional data about an image.
745
+
746
+
747
+ TO DO
748
+ =====
749
+
750
+ Please send bug reports, offers of help, etc. to jpeg-info@jpegclub.org.
751
+ ```
752
+
753
+ ## node-addon-api
754
+
755
+ ```text
756
+ The MIT License (MIT)
757
+
758
+ Copyright (c) 2017 [Node.js API collaborators](https://github.com/nodejs/node-addon-api#collaborators)
759
+
760
+ Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
761
+
762
+ The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
763
+
764
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
765
+ ```