OpenSite/Third-party notices
Find the notices that belong to the build you actually use.
Use the supplied notice pack
The application’s distributor should supply the notices for the exact binaries and configuration. The reviewed scientific-prefix process assembles a notices directory, including a scientific notice inventory and component licence texts. Preserve those files when keeping or transferring an authorized package. This page is an index, not a replacement for the complete texts.
Components to expect
| Area | Examples in the reviewed development work |
|---|---|
| Embedded scripting | CPython and pybind11 |
| Scientific Python | NumPy, SciPy, pandas, Matplotlib, SymPy and their actual compiled/runtime dependencies |
| Desktop | Qt and the components actually included in the desktop package |
| Numerical headers | Eigen in configurations/targets that use it |
Do not substitute another package’s notices
A package’s top-level licence is not necessarily the whole inventory: fonts, codecs, BLAS/LAPACK and compiler runtime components can carry additional notices. Debug and Release distributions also differ. The repository’s recorded Windows review does not establish a new public product release or permission for every future platform.
Questions about a received build
Retain the package name, build identifier and notice folder. Ask the distributor about missing notices or redistribution rights before distributing a modified package. Final product terms belong under OpenSite/Licensing.
