github.com/hashicorp/consul/envoyextensions safe for commercial use?Go module package · License: MPL-2.0 AND BUSL-1.1
github.com/hashicorp/consul/envoyextensions is licensed under MPL-2.0 AND BUSL-1.1. It carries a source-disclosure obligation, and all 5 shipping models below need a reading of the license itself.
| How you ship it | Result | Why |
|---|---|---|
| Hosted SaaS | Needs review | Multiple licenses apply at once. MPL-2.0 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / BUSL-1.1 is not an OSI-approved open source license. Licenses in this family commonly restrict offering the software as a commercial or competing service. The specific terms need individual review. |
| Distributed binary / app | Needs review | Multiple licenses apply at once. MPL-2.0 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / BUSL-1.1 is not an OSI-approved open source license. Licenses in this family commonly restrict offering the software as a commercial or competing service. The specific terms need individual review. |
| Delivered to customer | Needs review | Multiple licenses apply at once. MPL-2.0 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / BUSL-1.1 is not an OSI-approved open source license. Licenses in this family commonly restrict offering the software as a commercial or competing service. The specific terms need individual review. |
| Internal use only | Needs review | Multiple licenses apply at once. MPL-2.0 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / BUSL-1.1 is not an OSI-approved open source license. Licenses in this family commonly restrict offering the software as a commercial or competing service. The specific terms need individual review. |
| Published library | Needs review | Multiple licenses apply at once. MPL-2.0 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / BUSL-1.1 is not an OSI-approved open source license. Licenses in this family commonly restrict offering the software as a commercial or competing service. The specific terms need individual review. |
Source disclosureAttribution
If you only use it at build time, the answer changes.
Multiple licenses apply at once. MPL-2.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. / BUSL-1.1 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.
github.com/hashicorp/consul/envoyextensions is licensed under MPL-2.0 AND BUSL-1.1. It carries a source-disclosure obligation, and all 5 shipping models below need a reading of the license itself.
Multiple licenses apply at once. MPL-2.0 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / BUSL-1.1 is not an OSI-approved open source license. Licenses in this family commonly restrict offering the software as a commercial or competing service. The specific terms need individual review.
Multiple licenses apply at once. MPL-2.0 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / BUSL-1.1 is not an OSI-approved open source license. Licenses in this family commonly restrict offering the software as a commercial or competing service. The specific terms need individual review.
Multiple licenses apply at once. MPL-2.0 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / BUSL-1.1 is not an OSI-approved open source license. Licenses in this family commonly restrict offering the software as a commercial or competing service. The specific terms need individual review.
Multiple licenses apply at once. MPL-2.0 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / BUSL-1.1 is not an OSI-approved open source license. Licenses in this family commonly restrict offering the software as a commercial or competing service. The specific terms need individual review.
Multiple licenses apply at once. MPL-2.0 applies copyleft per file, not to your project as a whole. Files it covers must stay under it and their modifications must be published, while your own files may carry any terms you choose. It treats static and dynamic linking alike, so how you link makes no difference. / BUSL-1.1 is not an OSI-approved open source license. Licenses in this family commonly restrict offering the software as a commercial or competing service. The specific terms need individual review.
Multiple licenses apply at once. MPL-2.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. / BUSL-1.1 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 →The license was read from the repository's own LICENSE file, falling back to deps.dev and then ClearlyDefined — Go has no central license metadata, so a project's LICENSE at its default branch is the most direct answer to what it is licensed under today, 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.
License data last reviewed .
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.
Listed in the official MCP registry, on Glama and on Smithery. Source on GitHub (Apache-2.0).