CC-BY-NC-4.0 · Non-commercial only
Restricts use to non-commercial purposes. It grants no rights for commercial use, which rules it out for anything shipped by a business, including internal tooling that supports commercial activity.
The same license produces different obligations depending on whether the software is distributed, hosted, or kept internal. This is the distinction most dependency scanners collapse.
| How you ship it | Result | Why |
|---|---|---|
| Hosted SaaS | Obligation triggered | CC-BY-NC-4.0 permits non-commercial use only and does not grant rights for commercial use. |
| Distributed binary / app | Obligation triggered | CC-BY-NC-4.0 permits non-commercial use only and does not grant rights for commercial use. |
| Delivered to customer | Obligation triggered | CC-BY-NC-4.0 permits non-commercial use only and does not grant rights for commercial use. |
| Internal use only | Obligation triggered | CC-BY-NC-4.0 permits non-commercial use only and does not grant rights for commercial use. |
| Published library | Obligation triggered | CC-BY-NC-4.0 permits non-commercial use only and does not grant rights for commercial use. |
None
As a build-time dependency it is a different question.
CC-BY-NC-4.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.
Want to know whether anything in your project is under CC-BY-NC-4.0?
Check your whole manifest →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.