LicenseGuard

Is epaint_default_fonts safe for commercial use?

Rust crate package · License: (MIT OR Apache-2.0) AND OFL-1.1 AND Ubuntu-font-1.0

epaint_default_fonts is licensed under (MIT OR Apache-2.0) AND OFL-1.1 AND Ubuntu-font-1.0. It carries a source-disclosure obligation, and all 5 shipping models below need a reading of the license itself.

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

How you ship itResultWhy
Hosted SaaS Needs review Multiple licenses apply at once. This package offers a choice of licenses. The least restrictive option is shown. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. OFL-1.1 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / Ubuntu-font-1.0 does not match a known license identifier. The license text needs individual review.
Distributed binary / app Needs review Multiple licenses apply at once. This package offers a choice of licenses. The least restrictive option is shown. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. OFL-1.1 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / Ubuntu-font-1.0 does not match a known license identifier. The license text needs individual review.
Delivered to customer Needs review Multiple licenses apply at once. This package offers a choice of licenses. The least restrictive option is shown. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. OFL-1.1 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / Ubuntu-font-1.0 does not match a known license identifier. The license text needs individual review.
Internal use only Needs review Multiple licenses apply at once. This package offers a choice of licenses. The least restrictive option is shown. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. OFL-1.1 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / Ubuntu-font-1.0 does not match a known license identifier. The license text needs individual review.
Published library Needs review Multiple licenses apply at once. This package offers a choice of licenses. The least restrictive option is shown. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. OFL-1.1 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / Ubuntu-font-1.0 does not match a known license identifier. The license text needs individual review.

What obligations does epaint_default_fonts carry?

AttributionSource disclosure

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

Multiple licenses apply at once. This package offers a choice of licenses. The least restrictive option is shown. MIT 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. OFL-1.1 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. / Ubuntu-font-1.0 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.

Questions this page answers

Is epaint_default_fonts safe for commercial use?

epaint_default_fonts is licensed under (MIT OR Apache-2.0) AND OFL-1.1 AND Ubuntu-font-1.0. It carries a source-disclosure obligation, and all 5 shipping models below need a reading of the license itself.

Can I use epaint_default_fonts ((MIT OR Apache-2.0) AND OFL-1.1 AND Ubuntu-font-1.0) in hosted saas?

Multiple licenses apply at once. This package offers a choice of licenses. The least restrictive option is shown. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. OFL-1.1 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / Ubuntu-font-1.0 does not match a known license identifier. The license text needs individual review.

Can I use epaint_default_fonts ((MIT OR Apache-2.0) AND OFL-1.1 AND Ubuntu-font-1.0) in distributed binary / app?

Multiple licenses apply at once. This package offers a choice of licenses. The least restrictive option is shown. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. OFL-1.1 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / Ubuntu-font-1.0 does not match a known license identifier. The license text needs individual review.

Can I use epaint_default_fonts ((MIT OR Apache-2.0) AND OFL-1.1 AND Ubuntu-font-1.0) in delivered to customer?

Multiple licenses apply at once. This package offers a choice of licenses. The least restrictive option is shown. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. OFL-1.1 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / Ubuntu-font-1.0 does not match a known license identifier. The license text needs individual review.

Can I use epaint_default_fonts ((MIT OR Apache-2.0) AND OFL-1.1 AND Ubuntu-font-1.0) in internal use only?

Multiple licenses apply at once. This package offers a choice of licenses. The least restrictive option is shown. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. OFL-1.1 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / Ubuntu-font-1.0 does not match a known license identifier. The license text needs individual review.

Can I use epaint_default_fonts ((MIT OR Apache-2.0) AND OFL-1.1 AND Ubuntu-font-1.0) in published library?

Multiple licenses apply at once. This package offers a choice of licenses. The least restrictive option is shown. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. OFL-1.1 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / Ubuntu-font-1.0 does not match a known license identifier. The license text needs individual review.

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

Multiple licenses apply at once. This package offers a choice of licenses. The least restrictive option is shown. MIT 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. OFL-1.1 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. / Ubuntu-font-1.0 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.

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

Check your whole manifest →

How was this determined?

The license was read from crates.io, then evaluated against each shipping model. Dependencies in this ecosystem are linked statically, which is assumed here. 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).