mdn-data safe for commercial use?npm package · License: CC0-1.0
mdn-data is licensed under 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 | CC0-1.0 is a public-domain dedication or equivalent. It carries no conditions on use. |
| Distributed binary / app | No obligation | CC0-1.0 is a public-domain dedication or equivalent. It carries no conditions on use. |
| Delivered to customer | No obligation | CC0-1.0 is a public-domain dedication or equivalent. It carries no conditions on use. |
| Internal use only | No obligation | CC0-1.0 is a public-domain dedication or equivalent. It carries no conditions on use. |
| Published library | No obligation | CC0-1.0 is a public-domain dedication or equivalent. It carries no conditions on use. |
None
If you only use it at build time, the answer changes.
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.
A public-domain dedication rather than a license. The author waives all copyright interest to the extent legally possible, so no attribution or other condition attaches.
This page covers one package. Your package-lock.json has many more.
Check your whole manifest →The license was read from the npm 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.