Ownership
Proprietary software remains proprietary.
Unless a component is expressly identified as open source or otherwise licensed to you, GN-Apex software, source code, compiled binaries, interfaces, product designs, trademarks, service names, documentation, and other original materials are proprietary to GN-Apex or its applicable licensors.
Access to a GN-Apex service does not, by itself, transfer ownership of the underlying software. Your rights to use a hosted service are governed by the applicable service terms, subscription terms, or other agreement governing that service.
Open source
Open-source licenses are preserved.
GN-Apex incorporates open-source software. Each dependency remains subject to its own license. Nothing on this page is intended to replace the license text distributed with the corresponding component.
Where an open-source license grants rights that cannot be restricted by a downstream product license, those rights remain available to the extent required by the applicable license.
Component registry
Current attribution record.
The registry is deliberately readable: component, publisher, license, and the role the component plays in the application.
GN-Apex application code, product interfaces, service logic, branding, and other components identified as proprietary.
Dependency versions and transitive packages can change as the software is updated. The corresponding package manifests and distributed license notices remain the authoritative source for a particular build.
Attribution
License notices travel with the software.
Where a license requires copyright notices, attribution, disclaimers, or reproduction of license text, GN-Apex preserves those requirements in the applicable source, distribution, documentation, or license-notice bundle.
This page is a human-readable index. It is not a substitute for the complete license text of an individual component.
Commercial use
Your rights depend on the component.
Open-source components may be used, modified, and redistributed according to their individual licenses. Proprietary GN-Apex components are not granted those rights merely because they are delivered alongside open-source software.
Customers should review the service agreement and the applicable license notices before redistributing software, creating derivative works, extracting client libraries, or incorporating GN-Apex materials into another product.
Verification
We do not manufacture a license “validator.”
A licensing page should not pretend that a browser-side animation or generated hash proves the legal status of a package. The authoritative record is the actual license text, copyright notice, package metadata, and source distribution supplied with the relevant software.
If a customer needs a build-specific software bill of materials or license bundle, the build artifacts and package manifests—not this visual registry—should be used as the source of truth.
Questions
Need a build-specific notice?
For questions about a component, attribution, redistribution, or a specific GN-Apex software build, use the legal contact channel published on the website. Identify the product and release where possible; do not send credentials, private keys, or other secrets.