numpy safe for commercial use?PyPI package · License: BSD-3-Clause AND 0BSD AND MIT AND Zlib AND CC0-1.0
numpy is licensed under BSD-3-Clause AND 0BSD AND MIT AND Zlib AND CC0-1.0, which imposes no source-disclosure obligation in any of the shipping models below.
| How you ship it | Result | Why |
|---|---|---|
| Hosted SaaS | No obligation | Multiple licenses apply at once. BSD-3-Clause requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. 0BSD is a public-domain dedication or equivalent. It carries no conditions on use. / Multiple licenses apply at once. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. Zlib requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / CC0-1.0 is a public-domain dedication or equivalent. It carries no conditions on use. |
| Distributed binary / app | No obligation | Multiple licenses apply at once. BSD-3-Clause requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. 0BSD is a public-domain dedication or equivalent. It carries no conditions on use. / Multiple licenses apply at once. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. Zlib requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / CC0-1.0 is a public-domain dedication or equivalent. It carries no conditions on use. |
| Delivered to customer | No obligation | Multiple licenses apply at once. BSD-3-Clause requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. 0BSD is a public-domain dedication or equivalent. It carries no conditions on use. / Multiple licenses apply at once. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. Zlib requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / CC0-1.0 is a public-domain dedication or equivalent. It carries no conditions on use. |
| Internal use only | No obligation | Multiple licenses apply at once. BSD-3-Clause requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. 0BSD is a public-domain dedication or equivalent. It carries no conditions on use. / Multiple licenses apply at once. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. Zlib requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / CC0-1.0 is a public-domain dedication or equivalent. It carries no conditions on use. |
| Published library | No obligation | Multiple licenses apply at once. BSD-3-Clause requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. 0BSD is a public-domain dedication or equivalent. It carries no conditions on use. / Multiple licenses apply at once. MIT requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / Multiple licenses apply at once. Zlib requires retaining the copyright notice and the license text. There is no source-disclosure obligation. / CC0-1.0 is a public-domain dedication or equivalent. It carries no conditions on use. |
Attribution
If you only use it at build time, the answer changes.
Multiple licenses apply at once. BSD-3-Clause 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. 0BSD 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. 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. Zlib 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. / CC0-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 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.