# Open Source Notices — Karuiya 0.9.3.1

Karuiya's own application code is proprietary. The standard Karuiya 0.9.3.1
Windows package also contains separately licensed open-source components. The
licenses of those components remain in force and are not replaced or restricted
by Karuiya's terms.

The standard package uses the **LGPL-only distribution profile**. It does not
contain `program/ffmpeg-gpl`, libx264, libx265, a GPL-extension installer, the
`cryptography` package, or an active GPL-extension downloader. `GPL_EXTENSION.md`,
the disabled configuration file, and `licenses/GPL-3.0.txt` document a possible
future user-selected extension; their presence does not mean that the extension
is installed or active.

## Qt and PySide6

Karuiya uses the reviewed LGPL-eligible Qt 6.11.1 modules and
PySide6/Shiboken6 6.11.1 under the LGPLv3 option. They are distributed as shared
DLLs and Python extension modules in the onedir `_internal` tree. Qt Virtual
Keyboard and Qt PDF are not included in the 0.9.3.1 runtime.

Users may replace compatible shared libraries. Notwithstanding any restriction
applicable to Karuiya's proprietary code, users may reverse engineer Karuiya when
and only to the extent necessary to debug modifications to an LGPL-covered
library, as permitted by the applicable LGPL terms.

Exact upstream wheel names and hashes, official source-archive hashes, and the
module inventory are recorded in `licenses/PySide6` and `licenses/Qt`. Qt Image
Formats is retained for WebP support; its source archive includes the bundled
libtiff and libwebp sources and license texts. Replacement guidance is in
`QT_LIBRARY_REPLACEMENT.md`. The complete LGPLv3 text is in
`licenses/LGPL-3.0.txt`.

## Two separate FFmpeg installations

Karuiya contains two technically and evidentially separate FFmpeg uses:

1. `program/ffmpeg-lgpl` is FFmpeg/ffprobe
   `n7.1.5-12-g1fdbca85aa-20260801`, invoked as an external process for media
   analysis, thumbnails, waveforms, proxies, filters, export, and output
   verification. It is an LGPLv3-or-later shared build. Binary hashes, exact
   configure output, the FFmpeg source commit, and the BtbN build-script commit
   are under `licenses/FFmpeg-LGPL`.
2. Qt Multimedia's preview backend uses FFmpeg 7.1.3 shared DLLs supplied by the
   PySide6 6.11.1 wheel. These DLLs are used only by QMediaPlayer preview. Their
   reference hashes, build configuration, and source references are under
   `licenses/Qt`.

The two sets of FFmpeg DLLs must not be substituted for one another.

## Python and PyInstaller

The onedir includes the CPython 3.14.6 runtime under the Python Software
Foundation license. `Karuiya.exe` contains the PyInstaller 6.21.0 bootloader,
whose GPLv2-or-later license includes the PyInstaller Bootloader Exception
permitting its use in non-free programs. License texts and source/build-input
evidence are under `licenses/Python` and `licenses/PyInstaller`.

## Source package and checksums

The source package corresponding to the standard 0.9.3.1 Windows package is:

https://downloads.karuiya.org/releases/0.9.3.1/Karuiya-0.9.3.1-open-source-sources.zip

Its SHA-256 file is published at the same location with the `.sha256` suffix.
The matching binary package and its SHA-256 are published in the same release
directory. The source package contains the source archives listed in
`licenses/SOURCE_ARCHIVE_CHECKSUMS.txt`, exact upstream build-input references,
and component evidence files.

The exact final onedir inventory is covered by `licenses/manifests/*.sha256` and
the package-level `release_manifest.json`. `THIRD_PARTY_COMPONENTS.json` is the
machine-readable component ledger.

Some FFmpeg dependencies are selected by the archived BtbN build scripts. Their
official dependency-source cache and evidence are retained with the matching
source package. `licenses/FFmpeg-LGPL/ENABLED_DEPENDENCY_SOURCE_REQUIREMENTS.md`
describes that inventory.

For source availability questions, contact `support@karuiya.org` or visit
https://karuiya.org/support/.

This notice is an engineering inventory, not legal advice or a certification of
compliance. The applicable license texts govern each component.
