OreML is a proprietary application built on a substantial base of open-source software, spanning three dependency ecosystems: the Python interpreter and libraries that carry out every pipeline step, the Rust crates statically linked into the desktop application itself, and the JavaScript packages bundled into its interface — so that you install nothing yourself. That bundling is what makes the product work out of the box, and it is also why this page exists: most of those components are distributed under permissive licences that require their copyright and licence notices to be preserved in any distribution, including ours.
Describing OreML accurately means saying both halves: it is a proprietary application built on open-source components across all three ecosystems, never a wholly closed binary. The components below remain under their own licences, and nothing in our Terms & Conditions purports to change that.
The installer draws on three separate dependency sets, each with its own package manager and its own licence metadata: 303 Python distributions in the bundled runtime, 610 Rust crates statically linked into the desktop application, and 214 JavaScript packages bundled into its interface — 1,127 components in total. Once identical licence texts are deduplicated (the MIT licence text alone, for example, is shared by hundreds of separate packages), that reduces to 449 distinct licence texts, each reproduced once and followed by every component it covers, in a single notices file of roughly 2.9 MB. This page sets out the largest of the three, the bundled Python runtime, by licence family below, and reproduces, in the sections that follow, every component across all three ecosystems whose licence carries obligations beyond simple attribution. The complete per-component list for all three ecosystems, with the full licence text where a licence requires it, is available on request from support@oreml.com for any released build, regenerated from the exact dependency set that build actually ships.
The bundled Python runtime is assembled from the runtime requirement sets, and is smaller than the development environment used to build it. It is the largest of the three dependency sets, which is why it is the one broken out below by licence family; the Rust and JavaScript components are overwhelmingly under equally permissive terms — MIT, Apache-2.0, BSD, ISC, Zlib, and similar — and are listed individually, by package and licence, in the full notices file rather than summarised again here. Composition of the Python runtime by licence family:
| Licence family | Approx. count | What it requires of us |
|---|---|---|
| MIT | 66 | Preserve copyright and licence text |
| BSD (2- and 3-clause) | 50 | Preserve copyright, licence text, and disclaimer |
| Apache-2.0 | 49 | Preserve notices, state changes, include NOTICE where present |
| Python Software Foundation | 3 | Preserve copyright and licence text |
| Mozilla Public Licence 2.0 | 2 | File-level copyleft — see below |
| GNU LGPL v3 | 1 | Library copyleft — see below |
| Proprietary but redistributable | 17 | Redistribution under the vendor's own terms — see below |
A minority of the Rust crates in the desktop application's dependency tree — currently 157 of the 610 — do not declare a licence in their own package metadata. This is common in that ecosystem and does not mean a crate is unlicensed; it means our notices generator cannot state which licence applies without a manual check of that crate's own repository. Every such crate is named individually, by package and version, in the full notices file, so nothing here is hidden — only, for that subset, currently unresolved. If this affects you, or you can point us to the correct licence for one of them, contact support@oreml.com.
Used to read the binary Excel .xlsb format. The LGPL requires that the licence text accompanies the distribution and that you are able to replace this component with a modified version of your own. It is bundled as an ordinary, separately-replaceable Python package inside the runtime — not statically linked into, or compiled together with, any proprietary part of OreML — and its full licence text ships in the notices file described above. If you wish to substitute your own build of it, you may replace the package within the installed runtime directory.
The MPL is a file-level copyleft: it attaches to the files of those components themselves and does not extend to the rest of the application. certifi and tqdm are Python packages in the bundled runtime; colored, cssparser, cssparser-macros, dtoa-short, option-ext, and selectors are Rust crates statically linked into the desktop application; lightningcss is a JavaScript package bundled into its interface. All nine ship unmodified, with their licence text included. tqdm is additionally available under the MIT licence, which we also honour.
The optional GPU acceleration package contains 17 NVIDIA CUDA runtime libraries (CUDA 12.9 series, cuDNN 9.10, NCCL 2.27, cuSPARSELt 0.7). These are proprietary to NVIDIA Corporation and are redistributed under NVIDIA's own licence terms, whose text ships alongside them in the notices file. They are used unmodified, reverse engineering of them is prohibited by our Terms & Conditions Section 5 as those terms require, and they are subject to applicable export-control law. This package is downloaded only if your machine has a compatible NVIDIA GPU; it is never installed otherwise.
Some tools with stronger copyleft licences are used only on our own build machines and are not part of anything you download — notably the GPL-licensed profiling tools used during development. They impose no obligation on your copy because your copy does not contain them.
If you believe a component is bundled without its required notice, or a notice here is wrong, tell us at support@oreml.com and we will correct it. We would rather fix an attribution than argue about one.