Trademark Guidelines

Last updated July 25th, 2024

Below is our trademark policy inspired by Dagger’s. We want to make our policy easily accessible, so we have created some FAQs to help steer you in the right direction.

Please take a moment to read the policy in its entirety.

If you have any questions or doubts about your project using our trademark, please contact us at [email protected]. We are happy to help provide more guidance for your use case.

Trademark FAQs

Yes, as follows. To avoid confusion in the community, your repo must clearly show that it is not directly related to Tuist. We ask that you use the following naming convention: [YourProjectName]-for-Tuist.

I am a package manager. Am I allowed to package and distribute Tuist? Am I allowed to create my own package named Tuist?

Tuist is a registered trademark, including all casings such as “tuist” or “TUIST.”
You are not permitted to build from the source code and produce a package with a name that contains “Tuist” without express written permission.
Packaging separate components, such as the Tuist XcodeProj, under the name “Tuist” is not allowed.
You may distribute and refer to the unaltered binaries obtained directly from Tuist as “tuist” (lowercase) provided that the version and platform (OS and architecture) are correct and checksums are verified.
Installers may download unaltered binaries directly from Tuist, as long as checksums are verified.

If you are packaging other software related to Tuist and want to include “Tuist” in the name, then follow the GitHub repo naming convention outlined above.

If I fork the Tuist repo, can I continue to call it Tuist?

Sometimes. If you modify Tuist code for purposes other than bug fixes followed by pull requests to Tuist, you must rename the repository to avoid confusion. If the fork creates a commercially competitive solution or introduces security vulnerabilities, you may be required to change the repository name.

We suggest following this naming convention: [YourProjectName]-for-Tuist. If you want to use a different naming convention, please refer to the “use to indicate compatibility” section of our trademark policy. Contact [email protected] for guidance.

Tuist Trademark Policy

Tuist, GmbH reserves the right to change these guidelines at any time. You should periodically check these guidelines to ensure compliance.

The Marks

Our Marks consist of the following registered, unregistered, and/or pending trademarks, service marks, and logos which are subject to change without notice: Tuist, Tuist logo, and other designs or marks referred to in your specific license agreement.

“Fair Use” Of Trademarks

Limited fair use of our Marks is allowed to refer to Tuist products or services, provided:

The use is truthful and not misleading.
It does not imply improper association or sponsorship by Tuist.
It complies with applicable laws.

Prohibited Trademark Uses

You may not use Tuist Marks:

As part of your own trademark.
In a way likely to cause confusion about Tuist’s sponsorship or affiliation.
To disparage Tuist or its products.
In connection with unlawful activities.
In ways that diminish goodwill in the Marks.

Use To Indicate Compatibility

Third-party products may indicate compatibility with Tuist by using statements like “abc for Tuist,” provided they are factual and do not imply endorsement.

Do Not Use As Nouns, Plurals, or Possessive Forms

Correct: “Tuist software”
Incorrect: “Tuist’s features” or “Tuists”

Do Not Create Composite Marks

Tuist Marks must not appear as part of other marks or logos without prior approval.

Use Of The Marks In Open Source Code

Redistribution of Tuist in open source projects must make it clear the project is unofficial, for educational purposes, and indicate where to find the official release.

For additional details or to resolve uncertainties, contact [email protected].