LicenseGuard

Is golang.org/x/text safe for commercial use?

Go module package · License: BSD-3-Clause AND LicenseRef-scancode-google-patent-license-golang

golang.org/x/text is licensed under BSD-3-Clause AND LicenseRef-scancode-google-patent-license-golang, which imposes no source-disclosure obligation in any of the shipping models below.

Result by how you ship

How you ship itResultWhy
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. / LicenseRef-scancode-google-patent-license-golang requires retaining the copyright notice and the license text. There is no source-disclosure obligation.
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. / LicenseRef-scancode-google-patent-license-golang requires retaining the copyright notice and the license text. There is no source-disclosure obligation.
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. / LicenseRef-scancode-google-patent-license-golang requires retaining the copyright notice and the license text. There is no source-disclosure obligation.
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. / LicenseRef-scancode-google-patent-license-golang requires retaining the copyright notice and the license text. There is no source-disclosure obligation.
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. / LicenseRef-scancode-google-patent-license-golang requires retaining the copyright notice and the license text. There is no source-disclosure obligation.

What you have to do

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. / LicenseRef-scancode-google-patent-license-golang 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 go.sum has many more.

Check your whole manifest →

How this was determined

The license was read from ClearlyDefined, which curates license data for Go modules, then evaluated against each shipping model. Dependencies in this ecosystem are linked statically, which is assumed here. 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.