Open Source Notices

Components redistributed in veriCue packages

veriCue is proprietary commercial software. It is not open source and is not licensed to you under an open-source licence. Some veriCue packages do, however, redistribute third-party open-source components. This page identifies them, names their licences, and explains how to obtain their source or replace them - the obligations those licences place on us.

Every package carries the same information alongside the binaries, in its licenses/ directory, tied to the exact build you received: the file list, the versions, and a SHA-256 for each redistributed library. This page is a summary; the package is the authoritative record for the copy you have.

Qt

Packages that include the desktop veriCue Inspector redistribute the Qt libraries and plugins the Inspector needs, so that it runs without a separately installed Qt SDK. Qt is used under the GNU Lesser General Public License version 3 (LGPLv3), dynamically linked.

• Components: QtCore, QtGui, QtWidgets, QtNetwork and the platform, image-format and related plugins those require. The exact list, version and checksums are in licenses/qt/MANIFEST.md in your package.
• Licence text: shipped as licenses/qt/LGPL-3.0.txt and licenses/qt/GPL-3.0.txt.
• Replacing it: the Qt libraries sit beside the Inspector and are found through the binary's own search path. You may substitute your own compatible build; licenses/qt/RELINKING.md gives the exact steps per platform, and nothing in the veriCue licence agreement restricts that right.
• Corresponding source: for every Qt version veriCue redistributes, the release stores veriCue's own copy of the exact upstream source archive - verified against the checksum upstream publishes - under dl.vericue.dev/third-party/qt/<version>/, together with a record of how the shipped binaries were produced. Your package's licenses/qt/MANIFEST.md names that archive and its SHA-256. The written offer stands for three years either way: support@vericue.dev. See licenses/qt/SOURCE-OFFER.md.
• Third-party code inside Qt: accounted for in licenses/qt/THIRD-PARTY-IN-QT.md, limited to the components in the libraries actually shipped.

The veriCue Runtime - the part loaded into your application - is a different case: it carries no Qt of ours. It links against the Qt your application already loads, and no veriCue component places its own Qt on PATH, LD_LIBRARY_PATH or any plugin path of another process.

OpenSSL

The Windows package redistributes OpenSSL, which the Runtime uses to verify the signature on licence keys. OpenSSL is used under the Apache License 2.0; the licence and the notice identifying the exact build are shipped in licenses/openssl/.

Questions

Compliance questions, source requests and notices: support@vericue.dev.