LicenseGuard

Is ttfunk safe for commercial use?

Ruby gem package · License: Nonstandard AND GPL-2.0-only AND GPL-3.0-only

ttfunk is licensed under Nonstandard AND GPL-2.0-only AND GPL-3.0-only. That triggers obligations in 3 of the 5 common shipping models, so whether it is safe for you depends on how you ship.

Can I use ttfunk in SaaS, a distributed app, or internally?

How you ship itResultWhy
Hosted SaaS Needs review Multiple licenses apply at once. LicenseRef-lg-unreadable does not match a known license identifier. The license text needs individual review. / Multiple licenses apply at once. GPL-2.0-only triggers its obligations on distribution. Your distribution model is hosted SaaS, which is not distribution, so no obligation arises today. Shipping this software later — on-premises delivery, a binary, or a published library — would trigger whole-work source disclosure. / GPL-3.0-only triggers its obligations on distribution. Your distribution model is hosted SaaS, which is not distribution, so no obligation arises today. Shipping this software later — on-premises delivery, a binary, or a published library — would trigger whole-work source disclosure. Part of the declared expression could not be read as SPDX ("Nonstandard"), so it is not reflected above; that part still needs individual review.
Distributed binary / app Obligation triggered Multiple licenses apply at once. LicenseRef-lg-unreadable does not match a known license identifier. The license text needs individual review. / Multiple licenses apply at once. GPL-2.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is distributed binary or application, which triggers that obligation. / GPL-3.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is distributed binary or application, which triggers that obligation. Part of the declared expression could not be read as SPDX ("Nonstandard"), so it is not reflected above; that part still needs individual review.
Delivered to customer Obligation triggered Multiple licenses apply at once. LicenseRef-lg-unreadable does not match a known license identifier. The license text needs individual review. / Multiple licenses apply at once. GPL-2.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is software delivered to a customer environment, which triggers that obligation. / GPL-3.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is software delivered to a customer environment, which triggers that obligation. Part of the declared expression could not be read as SPDX ("Nonstandard"), so it is not reflected above; that part still needs individual review.
Internal use only Needs review Multiple licenses apply at once. LicenseRef-lg-unreadable does not match a known license identifier. The license text needs individual review. / Multiple licenses apply at once. GPL-2.0-only triggers its obligations on distribution. Your distribution model is internal use only, which is not distribution, so no obligation arises today. Shipping this software later — on-premises delivery, a binary, or a published library — would trigger whole-work source disclosure. / GPL-3.0-only triggers its obligations on distribution. Your distribution model is internal use only, which is not distribution, so no obligation arises today. Shipping this software later — on-premises delivery, a binary, or a published library — would trigger whole-work source disclosure. Part of the declared expression could not be read as SPDX ("Nonstandard"), so it is not reflected above; that part still needs individual review.
Published library Obligation triggered Multiple licenses apply at once. LicenseRef-lg-unreadable does not match a known license identifier. The license text needs individual review. / Multiple licenses apply at once. GPL-2.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is a published library, which triggers that obligation. / GPL-3.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is a published library, which triggers that obligation. Part of the declared expression could not be read as SPDX ("Nonstandard"), so it is not reflected above; that part still needs individual review.

What obligations does ttfunk carry?

Source disclosureSame license

If you only use it at build time, the answer changes.

Multiple licenses apply at once. LicenseRef-lg-unreadable appears as a dev dependency, so it is not part of the artifact you ship. Distribution-triggered obligations do not arise. Tools that emit code into your output, such as code generators, are a separate case worth checking individually. / Multiple licenses apply at once. GPL-2.0-only appears as a dev dependency, so it is not part of the artifact you ship. Distribution-triggered obligations do not arise. Tools that emit code into your output, such as code generators, are a separate case worth checking individually. / GPL-3.0-only appears as a dev dependency, so it is not part of the artifact you ship. Distribution-triggered obligations do not arise. Tools that emit code into your output, such as code generators, are a separate case worth checking individually. Part of the declared expression could not be read as SPDX ("Nonstandard"), so it is not reflected above; that part still needs individual review.

Questions this page answers

Is ttfunk safe for commercial use?

ttfunk is licensed under Nonstandard AND GPL-2.0-only AND GPL-3.0-only. That triggers obligations in 3 of the 5 common shipping models, so whether it is safe for you depends on how you ship.

Can I use ttfunk (Nonstandard AND GPL-2.0-only AND GPL-3.0-only) in hosted saas?

Multiple licenses apply at once. LicenseRef-lg-unreadable does not match a known license identifier. The license text needs individual review. / Multiple licenses apply at once. GPL-2.0-only triggers its obligations on distribution. Your distribution model is hosted SaaS, which is not distribution, so no obligation arises today. Shipping this software later — on-premises delivery, a binary, or a published library — would trigger whole-work source disclosure. / GPL-3.0-only triggers its obligations on distribution. Your distribution model is hosted SaaS, which is not distribution, so no obligation arises today. Shipping this software later — on-premises delivery, a binary, or a published library — would trigger whole-work source disclosure. Part of the declared expression could not be read as SPDX ("Nonstandard"), so it is not reflected above; that part still needs individual review.

Can I use ttfunk (Nonstandard AND GPL-2.0-only AND GPL-3.0-only) in distributed binary / app?

Multiple licenses apply at once. LicenseRef-lg-unreadable does not match a known license identifier. The license text needs individual review. / Multiple licenses apply at once. GPL-2.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is distributed binary or application, which triggers that obligation. / GPL-3.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is distributed binary or application, which triggers that obligation. Part of the declared expression could not be read as SPDX ("Nonstandard"), so it is not reflected above; that part still needs individual review.

Can I use ttfunk (Nonstandard AND GPL-2.0-only AND GPL-3.0-only) in delivered to customer?

Multiple licenses apply at once. LicenseRef-lg-unreadable does not match a known license identifier. The license text needs individual review. / Multiple licenses apply at once. GPL-2.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is software delivered to a customer environment, which triggers that obligation. / GPL-3.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is software delivered to a customer environment, which triggers that obligation. Part of the declared expression could not be read as SPDX ("Nonstandard"), so it is not reflected above; that part still needs individual review.

Can I use ttfunk (Nonstandard AND GPL-2.0-only AND GPL-3.0-only) in internal use only?

Multiple licenses apply at once. LicenseRef-lg-unreadable does not match a known license identifier. The license text needs individual review. / Multiple licenses apply at once. GPL-2.0-only triggers its obligations on distribution. Your distribution model is internal use only, which is not distribution, so no obligation arises today. Shipping this software later — on-premises delivery, a binary, or a published library — would trigger whole-work source disclosure. / GPL-3.0-only triggers its obligations on distribution. Your distribution model is internal use only, which is not distribution, so no obligation arises today. Shipping this software later — on-premises delivery, a binary, or a published library — would trigger whole-work source disclosure. Part of the declared expression could not be read as SPDX ("Nonstandard"), so it is not reflected above; that part still needs individual review.

Can I use ttfunk (Nonstandard AND GPL-2.0-only AND GPL-3.0-only) in published library?

Multiple licenses apply at once. LicenseRef-lg-unreadable does not match a known license identifier. The license text needs individual review. / Multiple licenses apply at once. GPL-2.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is a published library, which triggers that obligation. / GPL-3.0-only requires that a work incorporating it, when distributed, be licensed as a whole under the same terms with corresponding source made available. Your distribution model is a published library, which triggers that obligation. Part of the declared expression could not be read as SPDX ("Nonstandard"), so it is not reflected above; that part still needs individual review.

Does ttfunk matter if it is only a build-time or dev dependency?

Multiple licenses apply at once. LicenseRef-lg-unreadable appears as a dev dependency, so it is not part of the artifact you ship. Distribution-triggered obligations do not arise. Tools that emit code into your output, such as code generators, are a separate case worth checking individually. / Multiple licenses apply at once. GPL-2.0-only appears as a dev dependency, so it is not part of the artifact you ship. Distribution-triggered obligations do not arise. Tools that emit code into your output, such as code generators, are a separate case worth checking individually. / GPL-3.0-only appears as a dev dependency, so it is not part of the artifact you ship. Distribution-triggered obligations do not arise. Tools that emit code into your output, such as code generators, are a separate case worth checking individually. Part of the declared expression could not be read as SPDX ("Nonstandard"), so it is not reflected above; that part still needs individual review.

This page covers one package. Your Gemfile.lock has many more.

Check your whole manifest →

How was this determined?

The license was read from the Ruby gem registry, then evaluated against each shipping model. Only the declared license is considered; code copied into a project's own source files is not detected by this method.

License data last reviewed .

LicenseGuard reports information derived from published license texts and dependency manifests. It is not legal advice and using it does not create an attorney-client relationship. Results reflect license metadata as declared; they do not identify every obligation or violation. Consult qualified counsel for decisions that matter.

Listed in the official MCP registry, on Glama and on Smithery. Source on GitHub (Apache-2.0).