certifi safe for commercial use?PyPI package · License: MPL-2.0
certifi is licensed under MPL-2.0, which imposes no source-disclosure obligation in any of the shipping models below.
| How you ship it | Result | Why |
|---|---|---|
| Hosted SaaS | No obligation | MPL-2.0 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. |
| Distributed binary / app | No obligation | MPL-2.0 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. |
| Delivered to customer | No obligation | MPL-2.0 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. |
| Internal use only | No obligation | MPL-2.0 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. |
| Published library | No obligation | MPL-2.0 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. |
Source disclosureAttribution
If you only use it at build time, the answer changes.
MPL-2.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.
File-level weak copyleft. Modifications to MPL-licensed files must be released under MPL, but your own files in the same project are unaffected. This makes it unusually easy to combine with proprietary code.
This page covers one package. Your requirements.txt has many more.
Check your whole manifest →The license was read from the PyPI 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.
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.