License and trademark

MPL-2.0 licensing, source obligations and trademark policy.

Teksilo uses the unmodified Mozilla Public License 2.0. This page summarizes the license and the project’s separate trademark policy.

Using and distributing Teksilo

You may use Teksilo in commercial and closed-source applications. MPL copyleft applies to covered files, including modifications to them. Separate application files may use a license of your choice (Sections 1.7, 1.10 and 3.3).

When distributing a binary containing Teksilo, you must:

• Make the covered source, including your modifications, available under MPL-2.0.
• Tell recipients how to obtain that source promptly, at no more than the cost of distribution, and how to obtain the license (Sections 3.1 and 3.2).
• Preserve license, copyright, patent, warranty and liability notices, except to correct known factual inaccuracies (Section 3.4).
• Ensure the executable’s terms do not restrict recipients’ rights to the covered source (Section 3.2(b)).

These source-distribution obligations apply to unmodified Teksilo too. Private changes that are not distributed do not trigger them.

Source availability

Published crate archives and matching repository tags provide the upstream source. If you modify covered files, provide those modifications as well.

The required text-document and text-typeset dependencies have their own MPL-2.0 licenses and release versions.

Patents and secondary licenses

Section 2.1(b) grants a royalty-free patent license for contributors’ contributions. Initiating patent litigation alleging that a Contributor Version infringes a patent terminates the rights granted under Section 2.1 (Section 5.2).

Teksilo files do not carry the Exhibit B incompatibility notice. Section 3.3 permits inclusion in a Larger Work under the listed secondary licenses: GPL-2.0, LGPL-2.1, AGPL-3.0 or later versions, subject to that section’s terms.

Warranty and termination

Teksilo is provided “as is”, with the warranty disclaimer and liability limits in Sections 6 and 7. Additional support, warranty or indemnity obligations may be offered only on your own behalf, with the contributor protections required by Section 3.5.

License breaches terminate rights, subject to Section 5.1’s reinstatement provisions. These include provisional reinstatement on compliance, a 60-day notification condition and a 30-day cure period for a first notice. Section 5.3 preserves validly granted end-user licenses, excluding distributors and resellers.

Sections 10.1 and 10.2 permit use under the received MPL version or a later version published by the Mozilla Foundation.

Paid support and indemnification agreements are separate arrangements: support@ferntech.eu.

Other licenses

Bundled Inter, Noto Sans Arabic, Noto Sans Hebrew and JetBrains Mono fonts use SIL OFL 1.1. Optional bundled Roboto Flex also uses OFL 1.1 according to its metadata and upstream repository; its adjacent license note currently names Apache-2.0.

TRADEMARKS.md uses LicenseRef-Teksilo-Trademark-Policy and is separate from the MPL source license. Forks should provide their own policy.

The repository has no aggregated third-party license manifest or CI license compatibility scan. cargo audit checks security advisories only.

Contributions

Contributions use MPL-2.0 and require a DCO sign-off with git commit -s. There is no CLA. Sign-offs are checked by human review. See Get involved for setup and contribution rules.

Trademark

The Teksilo name, logo and wordmark identify FernTech’s project. MPL-2.0 does not grant trademark rights beyond its notice requirements. The separate TRADEMARKS.md policy is version 1.0, revised 2026-08-28.

The policy permits references in articles, talks and tutorials, and statements such as “Built with Teksilo” or “Teksilo-compatible widget”. Third-party package names must not imply official status. Prefer foo-teksilo or foo-for-teksilo; the policy requests that teksilo- be left for FernTech crates. This is a project policy, not a crates.io reservation.

Distributed forks require distinct names and branding. Do not imply that FernTech endorses or publishes a third-party project or service.

Upstream-based distribution packages may retain the name for security and bug backports, dependency adjustments, unbundling, build and packaging changes, and patches awaiting an upstream release. Packages that change behavior or public API, add or remove features, or ship from a fork need a distinct name. Ask trademarks@ferntech.eu if your patch set is unclear under the policy.

Teksilo is the subject of pending French trademark application No. 5292025, filed by FernTech in classes 9 and 42. Policy revisions are not retroactive; consult the version stated in TRADEMARKS.md for current terms.