Packaging documentation: source and notice mapping for six bundled libraries in 4.11.0.86 Linux contrib wheel

Start by inspecting the specified 4.11.0.86 wheel, its opencv_contrib_python.libs/ directory, and LICENSE-3RD-PARTY.txt, then review the linked PyPI release and the repository's packaging metadata. Done means documenting exact source packages and versions, build-recipe links, and corresponding notices for all six listed libraries, with any available SBOM or static-linking information.

Expected behaviour

The third-party notices or linked build metadata should make it possible to associate bundled native libraries with their source versions and copyright/licence notices.

Actual behaviour

While reviewing the official artifact opencv_contrib_python-4.11.0.86-cp37-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl, I could not locate a specific source/version and notice mapping for the six files below in its LICENSE-3RD-PARTY.txt.

Wheel SHA-256: c47c0ef1098461cdc6fa1cdce4c942b8ec974c87423f4b5951443d26bb9ae407

PyPI release

These members are under opencv_contrib_python.libs/:

I found the aggregate notices for FFmpeg, Qt, OpenSSL, PNG and xcb-related components, but could not associate the six files above precisely. This is not a claim that they cannot be used commercially; I am trying to complete the artifact-to-notice mapping.

Steps to reproduce / artifact scope

Inspect the above wheel's opencv_contrib_python.libs/ directory and LICENSE-3RD-PARTY.txt without importing or rebuilding the package.

• Platform: Linux x86_64, manylinux2014 / manylinux_2_17 wheel.
• Version: opencv-contrib-python 4.11.0.86, cp37-abi3 wheel used with CPython 3.11.
• The request deliberately concerns this published version; I have not asserted that it is the latest release.

Could you provide links to the exact source packages/versions, build recipe and corresponding notices for these files? A build SBOM and indication of additional statically linked components would also help, if available. Another wheel's similarly named library would not establish this artifact's provenance.

I checked #855 and searched for SBOM and the bundled library/licence names; I did not find an existing artifact-specific mapping. I am not requesting legal advice or a rebuild.

Issue submission checklist

• This is a binary packaging/documentation issue, not a generic OpenCV coding question.
• I read the README and understand that this repository provides the Python package build toolchain.
• The request relates to the pre-built binaries and their build/notice metadata.
• Latest version: intentionally reviewing the fixed 4.11.0.86 release described above.