Third-party components – where to find their licenses¶
nexxcite is built with components of other vendors and open source projects: libraries, browser scripts, fonts and the runtime of the container image. Their licenses require that the license texts and copyright notices are passed on with nexxcite. This chapter describes where you find them.
It is intended for administrators, operators and anyone who has to check the licenses of the software in use, for example a compliance or procurement department.
1. Third-party components at a glance¶
Every build of nexxcite carries a complete list of the third-party components it contains, with version, license and license text. You find it in two places:
| Where | What | Who can see it |
|---|---|---|
| "About nexxcite" in the user menu | Version and build date of nexxcite, licensee, and a searchable table of all components with their full license texts | Every signed-in user |
| Files next to the application in the container image | THIRD-PARTY-NOTICES.txt – all notices in one text file; THIRD-PARTY-LICENSES.json – the same in a machine-readable form |
Operators with access to the container |
Both show the same content and always belong to the build that is running. When nexxcite is updated, the list is updated with it.
2. The "About nexxcite" dialog¶
Open the user menu (your name or picture at the top right) and choose "About nexxcite".
The dialog shows:
- the product name, the version and the build date,
- "Licensed for …" with the licensee of the license key (see Licensing),
- a table of all components with "Library", "Version" and "License", together with the number of libraries and the date the list was collected.
The search field ("Search library, version or license...") filters the table – for example by the name of a library or by a license such as "Apache-2.0".
A click on a row opens the details of that component:
| Field | Meaning |
|---|---|
| "License" | Name of the license |
| "Copyright" | The copyright notice of the component |
| "Authors" | Authors as stated by the component |
| "Project" | Address of the project |
| "License online" | Address of the license on the web |
| "Note", "Remark" | Additional information, for example why a license applies |
| License text | The full license text shipped with this build |
"All libraries" returns to the table.
Some components are marked "Build time only". They are used to build nexxcite and are not part of the running application. They are listed for completeness.
The list is part of the application and is shown only to signed-in users. It is not published on a page that can be reached without signing in.
3. The files in the container image¶
Operators find two files in the directory of the application (/app in the container image):
| File | Content |
|---|---|
THIRD-PARTY-NOTICES.txt |
All components with copyright notice and license text, as one text document. This is the notice file that licenses such as Apache 2.0 ask for. |
THIRD-PARTY-LICENSES.json |
The same information in a machine-readable format, for example for your own license management |
To copy the files out of a running container, for example with Docker:
docker cp <container>:/app/THIRD-PARTY-NOTICES.txt .
4. How the list is created¶
The list is created automatically every time nexxcite is built. The build reads the components that are actually part of the application – including indirect dependencies – together with their license information, and adds components that are delivered as files (browser scripts, fonts, the runtime).
- A build stops when a component has no named license, no license text, or a license that has not been reviewed and approved by us. A component therefore cannot slip into a release unnoticed.
- The list is the same for every installation of the same version.
5. Licenses that are not permissive¶
Most components are under permissive licenses such as MIT, Apache 2.0 or BSD. A few are not; we have reviewed and approved their use. Among them are:
| Component | License | Remark |
|---|---|---|
| Hangfire | LGPL v3 | Used unchanged; the license text is shipped. |
| Syncfusion | Commercial license of the vendor | Licensed by invim for use within nexxcite |
| Parts of the Microsoft SQL Server client | Microsoft license terms | – |
The table in the "About nexxcite" dialog is authoritative for the build you run. Our assessment of a license is not legal advice; if your organisation has its own rules for third-party licenses, check the list against them.
6. Limitations¶
- The dialog is available only to signed-in users. Operators without an account read the files in the container image instead.
- A build made without collecting the licenses shows the hint "This build carries no list of external libraries." instead of the table. Official releases always carry the list.
7. Frequently asked questions¶
Do the license texts have to be passed on separately? No. The license texts and notices are part of every build – in the dialog and in the files of the container image. If you pass nexxcite on to third parties yourself, check your obligations with your own legal advisors.
Can users who are not administrators see the list? Yes. Every signed-in user can open "About nexxcite".
Is the list available without signing in? No. It is only shown inside the application. Operators find it in the container image.