Open-source license
The kookey software license and reuse terms are to be published after the canonical source and release are confirmed.
1.License status
kookey has not published a verified license for its original code, documentation, or visual assets, and the canonical source repository and release provenance have not been confirmed publicly. Viewing or downloading material does not establish permission to redistribute it. Before asking people to reuse or self-host the software, the project will publish the chosen license, its identifier, the files it covers, and an authoritative license copy for each release.
2.Third-party components and assets
A dependency list is not a complete license or attribution inventory for every component, font, icon, photograph, illustration, or other asset. A release should include reviewed third-party notices or a software bill of materials that identifies each component, version, license, attribution requirement, and source. A dependency’s license applies to that dependency; it does not automatically license kookey’s original code or brand.
3.Contributing and attribution
kookey has not published contribution terms or said how it will receive rights to submitted code and creative work. Contribution reuse terms have not been published yet. We’ll explain how contributions may be used before accepting contributions under a named license. When contributing imported material, include its source, reuse terms, and any required attribution.
4.Name, logo, and press assets
Rights in a software license and rights in the kookey name, logo, or other brand assets can be different. The project license and any brand-asset permissions have not been confirmed. We’ll publish reuse guidance and approved press assets after those rights are settled. Do not imply endorsement or official affiliation by using the name or logo.
5.Report a licensing concern
A dedicated license contact has not been confirmed. The site lists contact@kookey.me for project inquiries, but mailbox monitoring is not verified. A monitored route and instructions for identifying the affected file, release, and source will be added with the published license and component notices.