Repository navigation
EN License and Contributing
English · Türkçe · Languages / Diller
Scope: JSON API Forge 0.5.1 · Source review: 17 September 2026 · Language: English
JSON API Forge uses the Source-Available Self-Host License 1.1 (LicenseRef-JAF-SASH-1.1). This page explains the reviewed project documents and grants no additional license rights. In a conflict, the LICENSE supplied with your copy controls.
| Use | Summary of the license |
|---|---|
| Source inspection, testing and auditing | Permitted use |
| Personal/commercial self-hosting | Permitted subject to conditions |
| Private/internal modifications | Permitted subject to conditions |
| Providing a backend as a network service | Permitted where users do not receive a software copy |
| Redistributing the framework or modified copies | Prohibited without separate written permission, subject to the narrow contribution exception |
| Community edition, rebranding, package/container mirror | Separate written permission required |
| Linking to the official repository/release | Supported sharing route |
Public GitHub source supports transparency, auditing, support and controlled contributions. It does not create an alternative distribution right. Official release authority is managed by Cavanşir Qurbanzadə (@Cavanshirpro) or a lawful successor/assignee. A GitHub organization transfer alone does not establish assignment of all intellectual-property rights.
Section 4 permits limited platform forks solely to propose contributions to the official repository. Preserve licenses/notices and clearly identify the fork as unofficial. Do not publish releases, installers, binaries, packages or independent distributions through that fork. This is not a general redistribution license.
Read CONTRIBUTING.md, CONTRIBUTOR_LICENSE_AGREEMENT.md and CODE_OF_CONDUCT.md. Target the branch owning the relevant product. PR acceptance does not grant the contributor official release-publishing authority.
Qt, Python and other dependencies retain their own licenses. This project's source-available license does not remove rights granted by those dependencies. Preserve required notices, license copies and applicable source/relinking obligations in portable and installer packages. THIRD_PARTY_NOTICES.md is the project guide for this area.
Follow TRADEMARK_POLICY.md and BRAND.md for names, logos and domains. Accurate compatibility statements differ from presenting a derivative as an official sponsored product. AI assistance does not remove human review, provenance or contributor responsibility; follow AI_USAGE_POLICY.md.
Report ordinary bugs/features with the relevant component and a reproducible example. For vulnerabilities, follow the current SECURITY.md; keep tokens, personal data and exploit details out of inappropriate public channels. Wiki changes follow the same source-accuracy and centralized-publication approach.
This page describes the behavior at the pinned commits below. Recheck these contracts when upgrading.
main/LICENSEmain/LICENSE-FAQ.mdmain/CONTRIBUTING.mdmain/CONTRIBUTOR_LICENSE_AGREEMENT.mdmain/THIRD_PARTY_NOTICES.mdmain/TRADEMARK_POLICY.mdmain/AI_USAGE_POLICY.md