Unlicense · Public domain dedication
A public-domain dedication for software. Functionally similar to CC0 with simpler wording, imposing no conditions on use.
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 | No obligation | Unlicense is a public-domain dedication or equivalent. It carries no conditions on use. |
| Distributed binary / app | No obligation | Unlicense is a public-domain dedication or equivalent. It carries no conditions on use. |
| Delivered to customer | No obligation | Unlicense is a public-domain dedication or equivalent. It carries no conditions on use. |
| Internal use only | No obligation | Unlicense is a public-domain dedication or equivalent. It carries no conditions on use. |
| Published library | No obligation | Unlicense is a public-domain dedication or equivalent. It carries no conditions on use. |
None
As a build-time dependency it is a different question.
Unlicense 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 Unlicense?
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.