|
This certificate confirms that your software project’s licensing has been reviewed and validated. It indicates that the selected licence has been verified for compatibility with all components, appropriately and transparently declared, and that the software is ready for compliant release when it comes to licensing and reasonable dependency checks.
The certificate builds upon the Verified Dependencies Certificate, extending its scope to include licence selection, Software Licence Analysis (SLA) review, and approval of required artefacts. The certificate remains valid indefinitely for future software versions, provided certification requirements continue to be met. It does not cover patents or legal liability, although patent concerns may be addressed during the SLA review.
A full specification of software licensing certificates is also available for GÉANT participants.
Ensure your software project:
Is intended for distribution
Has all direct and transitive dependencies identified and verified
Uses a clear software licence compatible with all dependencies, confirmed by the GÉANT IPR Manager
Also ensure that:
Identify all direct and transitive dependencies. You may use the GÉANT Software Composition Analysis (SCA) service, or obtain a Verified Dependencies Certificate.
Document all external libraries, code, and other third-party intellectual property used in the project.
Record the licences of all external components.
Manually review all third-party intellectual property (source code, content, designs, models, etc.), which may be recorded in the NOTICE file.
Address all critical vulnerabilities, typically by upgrading dependencies.
Initiate the GÉANT Software Licence Analysis (SLA) service, conduct an internal review, or rely on an equivalent process.
Confirm that all dependency licences are compatible with the selected licence.
Document any conflicts, resolutions, and rationales.
Use the GÉANT SLA service, or the Software Artefacts Checklist and templates for GÉANT participants.
Mandatory artefacts:
LICENSE – full text of the selected licence
COPYRIGHT – copyright notices and attributions
README – includes basic information, licence declaration, and copyright
If applicable or required by the licence:
NOTICE – third-party notices and attributions
CHANGELOG – version history, including licence-related changes
CONTRIBUTING – contribution policy or guidelines
Ensure that artefacts clearly and explicitly declare the selected licence, copyright ownership, and are in compliance with the terms of all dependencies.
Declare the licence in:
Repository metadata or settings
Software user interface (if required by the licence)
Documentation, help files, and release notes
Send a request to the Licence Management Team, including:
Results of the SLA or equivalent review
Access to the repository with all relevant artefacts
Supporting documentation or clarifications, such as descriptions of third-party components or internal reports on dependencies, licences, and vulnerabilities
Refer to Contact Us for instructions on communicating with the team.
Cooperate with the Licence Management Team to:
Provide requested clarifications
Remediate licence conflicts or vulnerabilities
Update artefacts and documentation as needed
Upon approval, your project will receive the Verified Software Licence Certificate, visible at certificates.software.geant.org and in the GÉANT Software Catalogue.
Reference the certificate in documentation, metadata, project pages, or communications. The Licence Management Team will provide guidance on how to do this.
To keep the certificate valid:
Inform the Licence Management Team of any major project changes that may affect licensing and IPR.
Respond to compliance-related queries from users or third parties.
Substantial changes to the software’s architecture, licensing model, or component replacements under a different licence may require revalidation.
The certificate is valid indefinitely, provided issues are promptly addressed and certification requirements continue to be met.
The Licence Management Team may periodically check the software and request revalidation if necessary.
Integrate SCA scanning into the CI/CD pipeline to detect licence or vulnerability issues early, and maintain long-term compliance.