# Third-party licence material shipped with Toolun

This directory is copied verbatim into every release build as `/LICENSES/` (see `scripts/build-cloudflare.mjs`;
the hardening step refuses to produce a build when any of the files listed below is missing).

| Component | Version | Licence | Material |
| --- | --- | --- | --- |
| `@ffmpeg/core` (FFmpeg compiled to WebAssembly) | 0.12.10 | GPL-2.0-or-later | [`ffmpeg-core/`](./ffmpeg-core/README.md): licence text (`COPYING.txt`), version, unmodified-distribution statement, source-code availability |
| `@imgly/background-removal` | 1.7.0 | AGPL-3.0-only | [`imgly-background-removal/`](./imgly-background-removal/README.md): licence text (`LICENSE.md`), version, source-code availability, notice that the module ships as a separate un-obfuscated chunk |
| Apache-2.0 assets (MediaPipe tasks-vision WASM and models, Tesseract `tessdata`) | see `docs/licenses/NOTICE.md` | Apache-2.0 | [`common/Apache-2.0.txt`](./common/Apache-2.0.txt) |
| Noto Sans SC, Liberation Sans | see `docs/licenses/NOTICE.md` | SIL OFL 1.1 | [`common/OFL-1.1.txt`](./common/OFL-1.1.txt) |
| All other bundled npm dependencies | per package | MIT / Apache-2.0 / BSD / ISC | generated at build time by Vite into `/LICENSES/third-party.md` |

The engineering compliance record (what is distributed, from where, with which obligations) is
`docs/licenses/NOTICE.md` in the repository. It is a self-audit, not legal advice.

## Where things run

- The ffmpeg core is **not** part of the static site. The application downloads it at runtime from the asset origin
  (`VITE_ASSET_ORIGIN`, an R2 bucket populated by `npm run export:external-assets`) or, as a fallback, from jsDelivr
  for the exact version above. The licence text and this notice are served from the same locations.
- The imgly background-removal module is bundled as an isolated chunk (`/assets/vendor-imgly-*.js`) that is
  excluded from every hardening/obfuscation transform, so recipients receive it in the form published by the author.

## Contact

Requests for corresponding source or licence questions: open an issue at <https://github.com/Yanuy/toolun> or write
to the address published on <https://toolun.com/about/>.